|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)|
|Tripe test failure update email@example.com (Nils M Holm) (2014-05-04)|
|Re: Triple test failure update firstname.lastname@example.org (Chris Dodd) (2014-05-23)|
|Re: Triple test failure update email@example.com (Nils M Holm) (2014-05-23)|
|Re: Triple test failure update firstname.lastname@example.org (2014-05-23)|
|From:||Chris Dodd <email@example.com>|
|Date:||Fri, 23 May 2014 01:50:19 +0000 (UTC)|
|Organization:||A noiseless patient Spider|
|References:||14-05-003 14-05-004 14-05-008|
|Posted-Date:||22 May 2014 23:00:31 EDT|
"Nils M Holm" <firstname.lastname@example.org> wrote in news:email@example.com:
> The assembly output of scc1 and scc2 is identical, the binaries are not.
> *Both* compilers seem to work perfectly fine.
So the difference is in the assembler or the linker.
Have you tried turning off ASLR (address space randomization)? You
can do this on linux with
# echo 0 > /proc/sys/kernel/randomize_va_space
If there is anything in the assembler or linker that depends on
addresses allocated in memory (such as hash tables?) then ASLR will
move things around, which may result in things being processed in a
different order and laid out differently.
Return to the
Search the comp.compilers archives again.