cross compiled output differs

[Richard Biener]

On Sat, Mar 10, 2018 at 12:58 PM, Milan Ton <milan.ton@yandex.ru> wrote:
> Hi:
>
> I built two versions -- linux/mingw -- of a 32-bit gcc cross compiler
> of codebase 7.3.0 on fedora 20 (gcc 4.8). Then I compiled an embedded
> project using the both cross compilers in the same build
> environment. An assemble code inspection showed that one function out
> of about thousand project functions differs in the two builds. Both
> run-time tests and visual inspection suggest that both variants of the
> compiled function are correct. I looked at the output of the switch
> `-fdump-tree-all' and realized that the path `ivopts' makes this difference.
> Once `-fno-ivopts' applied, the two compilations are binary equivalent.
>
> Shouldn't I expect in general same output of such cross compilers ?
> What could be reasons of such differences ? and options to fix it ?

Not sure if I understand but if one cross compiler targets linux-32bit and one
targets mingw-32bit then of course there are differences to be expected.

If I didn't understand please correct the two cross compiler host/target combos
below

 x86_64-fedora -> i586-linux
 x86_64-fedora -> i586-mingw32

> Milan