* Moffett, Kyle D | 2010-04-22 19:17:17 [-0500]: >Not really... If you build GCC with "--enable-e500_double" it produces code >that is not quite binary compatible with code generated without that option, >because it indicates that the GPRs have an extra shadow 32 high bits that >can be only accessed by certain FPU operations. I believe it affects >function stack layout and calling conventions (one GPR versus two). The stack on powerpc has an alignment of 16 bytes due to AltiVec. The double type arguments are passed in two 32bit grp registers. The kernel can emulate those Opcodes if there are not availble. I know some one run my port on a G5 for testing. So yes we can mix it and no I don't want it because it will be slow.
>As far as compile hardware goes... If I can get one buildd set up locally >then I have 6 NFS-booting e500v2 boards to throw at the problem; each with a >dual-core P2020 chip @ 1GHz, 2GB 533MHz registered ECC RAM, and an Intel >160GB gen-2 SSD. Okay. So I will redirect all OpenOffice builds to your machines :) >Kyle Moffett Sebastian -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
