On Sat, 24 Oct 2009, Gabe Black wrote: > > The getSyscallArg function can be defined differently for different > types of processes, typically 32 bit vs. 64 bit. Defining those > differently might do it. It could be more complicated than that if, for > instance, the number of register pairs is dependent on the syscall so > the location of argument n depends on how many pairs that particular > syscall uses before getting to n. In any case, I think the process > object would be a good place for a fix.
it depends on both of those (the syscall itself and also the exact types of the preceeding arguments). So it makes it more troublesome. I'll be sending an x86 truncate64 patch soon. It shows what is needed to get x86 working. It might need some extra fixing for the power and other 32-bit architectures because I'm not sure if the current code is handling endianess issues properly. Vince _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
