Re: Triple test failure update

Chris Dodd <cdodd@acm.org>
Fri, 23 May 2014 01:50:19 +0000 (UTC)

          From comp.compilers
Related articles
Mysterious triple test failures nmh@t3x.org (Nils M Holm) (2014-05-03)
Re: Mysterious triple test failures kaz@kylheku.com (Kaz Kylheku) (2014-05-03)
Tripe test failure update nmh@t3x.org (Nils M Holm) (2014-05-04)
Re: Triple test failure update cdodd@acm.org (Chris Dodd) (2014-05-23)
Re: Triple test failure update nmh@t3x.org (Nils M Holm) (2014-05-23)
Re: Triple test failure update alexfrunews@gmail.com (2014-05-23)
| List of all articles for this month |
From: Chris Dodd <cdodd@acm.org>
Newsgroups: comp.compilers
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
Keywords: debug, linker
Posted-Date: 22 May 2014 23:00:31 EDT

"Nils M Holm" <nmh@t3x.org> wrote in news:14-05-008@comp.compilers:
> 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.


Chris Dodd
cdodd@acm.org

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.