Selon Paolo Bonzini <[EMAIL PROTECTED]>: > > > This will need some additionals tests on MULTILIB in the > LIBGNAT_TARGET_PAIRS > > machinery (3 files for x86 vs x86_64, solaris looks like already done, > powerpc > > seem 32 bits only right now, s390/s390x, others?) but it doesn't seem like > a > > blocking issue with the proposed design since each MULTILIB rts build has > > completely separate directory and stamp (through RTSDIR) so there is no > > possibility of conflict through sharing. > > > > Do you agree with this assessment? > > Unfortunately not. The solaris bits are just "factoring" a bit the > definition of LIBGNAT_TARGET_PAIRS. The actual multilib definition can > be arbitrary, for example you can have big-endian/little-endian > multilibs. If the design is explicitly to have constants spelled out in > system-* files (instead of having them, for example, in Autoconf > macros), there is not much that you can do.
There is a Standard'Default_Bit_Order so it's the same as Word_Size: we just loose "source" documentation (and gain less diff between target file). There is some code in the Ada RTS that explicitely check for big endian/little endian (so will work on both, see g-socket.adb Short_To_Network), I doubt that there is RTS code that makes an implicit assumption about this (if there is it's most likely a bug). Laurent
