Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!news.misty.com!news.iecc.com!.POSTED!nerds-end From: Chris Dodd Newsgroups: comp.compilers Subject: Re: Triple test failure update Date: Fri, 23 May 2014 01:50:19 +0000 (UTC) Organization: A noiseless patient Spider Lines: 18 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-05-027@comp.compilers> References: <14-05-003@comp.compilers> <14-05-004@comp.compilers> <14-05-008@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: miucha.iecc.com 1400814031 19001 2001:470:1f07:1126:0:676f:7373:6970 (23 May 2014 03:00:31 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Fri, 23 May 2014 03:00:31 +0000 (UTC) Keywords: debug, linker Posted-Date: 22 May 2014 23:00:31 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1252 "Nils M Holm" 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