|Mysterious triple test failures email@example.com (Nils M Holm) (2014-05-03)|
|Re: Mysterious triple test failures firstname.lastname@example.org (Kaz Kylheku) (2014-05-03)|
|Re: Mysterious triple test failures mrs@Kithrup.COM (2014-05-04)|
|Re: Mysterious triple test failures email@example.com (Nils M Holm) (2014-05-04)|
|Re: Mysterious triple test failures firstname.lastname@example.org (2014-05-04)|
|From:||mrs@Kithrup.COM (Mike Stump)|
|Date:||Sun, 4 May 2014 04:47:18 GMT|
|Organization:||Kithrup Enterprises, Ld.|
|Posted-Date:||04 May 2014 15:28:52 EDT|
In article 14-05-003, Nils M Holm <email@example.com> wrote:
>Now it has happened that this test failed, resulting in stage-1
>and stage-2 compiler of identical size, but with tens of thousands
>of differences. However, both compilers seem to work fine. The
>differences are not in the symbol table, stripping the binaries
>did not make any difference.
objdump -s, onjdump -d, objdump -h are your friends... You can do
dumps and compare those outputs... Also, for production comparisons,
come over to gcc (gcc.gnu.org) land, we have comparisons methods that
work across lots of machines and can deal with things like embedded
file time stamps and the like.
Return to the
Search the comp.compilers archives again.