This patch is similar to but not the same as what I described earlier. Instead of keeping track of a stack pointer in the background in the process or threadcontext where it could end up out of sync, not being updated properly in subclasses, getting trashed in multithreaded environments, etc., I put the index into the syscall functions using a reference argument. This had the nice (to me at least) property of not introducing another set of functions. All the quick regressions pass except memtest-ruby. I made ftruncate64 use the new capabilities of this setup, but it doesn't appear to be used by any ISA so I can't really test it explicitly. Also, I only put in special rules for 32 bit x86. It sounds like other ISAs have other rules which I'm not necessarily familiar with. It should be easy to fix them up using I386LinuxProcess as an example.
Gabe Gabe Black wrote: > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
