Roland McGrath <rol...@redhat.com> writes: > Is there any actual benefit to arch=powerpc64 and the separate directory of > files that all just #include the powerpc files? I think we'd do as well > just to leave arch=powerpc for the powerpc64 configuration. It doesn't > seem likely that these lists will diverge for ppc32/ppc64 in the future.
Actually I originally planned to make the ppc64 syscall table different from the ppc32 table, leaving out the unimplemented and 32-bit only syscalls. > To support those systems more smoothly, we could also make ppc32 > strace use PTRACE_GETREGS64 to support ppc64 tracees, but that would > require much more work in the inverse biarch decoding support. There are a lot of places that assume you can read sizeof(long) worth of data from the u-area to read a register's contents. That won't work on ppc32 targeting ppc64 whereas it works fine the other way round. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
