Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border4.nntp.dca.giganews.com!backlog4.nntp.dca3.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end From: "Nils M Holm" Newsgroups: comp.compilers Subject: Re: Triple test failure update Date: Fri, 23 May 2014 09:09:11 +0200 Organization: Compilers Central Lines: 38 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-05-028@comp.compilers> References: <14-05-003@comp.compilers> <14-05-004@comp.compilers> <14-05-008@comp.compilers> <14-05-027@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: miucha.iecc.com 1400863544 17044 2001:470:1f07:1126:0:676f:7373:6970 (23 May 2014 16:45:44 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Fri, 23 May 2014 16:45:44 +0000 (UTC) Keywords: storage, debug Posted-Date: 23 May 2014 12:45:44 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com X-Original-Bytes: 2289 Xref: csiph.com comp.compilers:1253 Chris Dodd wrote: > 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. Ah, this is interesting! I had previously thought about ASLR, but then thought that it cannot affect executables as long as they merely sit on the hard disk. Your comment sheds new light on this aspect. Unfortunately, I have never been able to reproduce this behavior myself (only heard about it from testers) and currently it does not seem to be reproducible anywhere. This happened after I changed the Makefile from scc *.c to scc $(SRC) so it looks like John and a few others here in c.c. where right. It was most probably the order of objects passed to the linker. However, should the problem re-appear, I will definitely try what you suggested! Thanks! Nils -- Nils M Holm < n m h @ t 3 x . o r g > www.t3x.org