cross compiled output differs

[Milan Ton]

Nathan, Richard:

sorry if it wasn't clear: my target was a 32-bit embedded system for that
I built two cross compilers to be run on two hosts -- linux32 and mingw32 --,
my build system was Fedora x86_64 (with gcc -m32 and i686-w64-mingw32-gcc
respectively). So Nathan's scheme was what I would have depicted:
> host:linux -> some (embedded) system
> host:mingw32 -> same (embedded) system

>> Shouldn't I expect in general same output of such cross compilers ?
>> What could be reasons of such differences ? and options to fix it ?

> Yes, that's a reasonable expectation. The usually discovered cause of
> such differences is the host system's qsort function coupled with a
> comparison function that can return 0. When that happens things can be
> differently ordered, essentially at the whim of the host. And that can
> affet code generation.

This is really useful. Thanks a lot !

> If you could find a selfcontained testcase, that'd make a great bug
> report.

I'll try to think of a reproducible test-case.

Milan