> In particular, isn't it a known issue that 32-bit hosts and 64-bit hosts can
> generate different constant-loading sequences owing to the differing size of
> HOST_WIDE_INT?
>
> Was that 32-bit Solaris?
>
> cheers,
> DaveK
As a followup, I built a 32-bit version of the entire toolchain and it pro
> In particular, isn't it a known issue that 32-bit hosts and 64-bit hosts can
> generate different constant-loading sequences owing to the differing size of
> HOST_WIDE_INT?
>
> Was that 32-bit Solaris?
>
> cheers,
> DaveK
The system is 64-bit Solaris 9 but the native gcc is sparc-sun-solaris2.9
> In my experience, there's all kinds of reasons why this can happen.
>
> Use of floating point within the compiler (we generally avoid it),
> unstable qsort (again, we generally try to avoid it), hashing issues,
> particularly with pointers, etc etc.
>
> For those reasons and many more, we don't t
Hi,
I am attempting to move an old gcc powerpc-eabi cross toolchain from an old
Solaris SPARC server to a new Linux x86_64 server. I have built and installed
the exact same cross-binutils (2.13.2.1), cross-gcc (3.2.3) and cross-newlib
(1.11.0) from source using the exact same target (powerpc-e
