public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lars dot sonchocky-helldorf at hamburg dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/18972] Regression: bootstrap failure of gcc-4.0-20041212 on OpenDarwin 7.2.1/x86 (i686-apple-darwin7.2.1): Bootstrap comparison failure Date: Tue, 14 Dec 2004 13:46:00 -0000 [thread overview] Message-ID: <20041214134629.22440.qmail@sourceware.org> (raw) In-Reply-To: <20041214004742.18972.lars.sonchocky-helldorf@hamburg.de> ------- Additional Comments From lars dot sonchocky-helldorf at hamburg dot de 2004-12-14 13:46 ------- Well next time I better read http://gcc.gnu.org/install/build.html thoroughly instead of just banking on the "word of irc" instead: It had to be 'BOOT_CFLAGS' instead of 'BOOTCFLAGS' of course. Anyway, surprisingly 'make bootstrap STAGE1_CFLAGS="-no-cpp-precomp -Wa,-force_cpusubtype_ALL" BOOT_CFLAGS="-O2 -g -save-temps"' worked flawlessly - no Bootstrap comparison failure any more. I also came to know that '-save-temps' doesn't save the .i and .s files in the stageX directories but just in the gcc directory (so the stage2 .i and .s files would get erased by a bootstrap or bubblestrap) So I started over like this: cd GCC/FSF/gcc-build/ rm -rf * ../gcc-4.0-20041212/configure --prefix=/tmp/gcc make bootstrap STAGE1_CFLAGS="-no-cpp-precomp -Wa,-force_cpusubtype_ALL" cd gcc redoing stage 2 (note the additional '-fomit-frame-pointer' (which I omitted in the first place too ;-))): touch ../../gcc-4.0-20041212/gcc/reload.c make restage2 BOOT_CFLAGS="-O2 -g -fomit-frame-pointer -save-temps" now I moved reload.i and reload.s into a safe place and then redoing stage 3: touch ../../gcc-4.0-20041212/gcc/reload.c make restage3 BOOT_CFLAGS="-O2 -g -fomit-frame-pointer -save-temps" then I saved the "other" reload.i and reload.s too The comparison of all stage2 vs. stage3 files yieled absolutelly no difference (even the .o files are similar) Heisenbug? Next thing I'll do is a clean 'make bootstrap STAGE1_CFLAGS="-no-cpp-precomp -Wa,-force_cpusubtype_ALL" BOOT_CFLAGS="-O2 -g -fomit-frame-pointer"' and then again the same with '-save-temps' added to see which (if?) one of those fails. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18972
next prev parent reply other threads:[~2004-12-14 13:46 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-14 0:47 [Bug bootstrap/18972] New: " lars dot sonchocky-helldorf at hamburg dot de 2004-12-14 0:50 ` [Bug bootstrap/18972] " lars dot sonchocky-helldorf at hamburg dot de 2004-12-14 0:54 ` pinskia at gcc dot gnu dot org 2004-12-14 1:27 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-14 13:46 ` lars dot sonchocky-helldorf at hamburg dot de [this message] 2004-12-14 16:18 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-14 16:21 ` pinskia at gcc dot gnu dot org 2004-12-18 5:18 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-18 5:20 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-18 5:21 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-18 5:22 ` lars dot sonchocky-helldorf at hamburg dot de 2004-12-18 5:39 ` lars dot sonchocky-helldorf at hamburg dot de 2005-01-04 0:48 ` lars dot sonchocky-helldorf at hamburg dot de 2005-01-04 0:52 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20041214134629.22440.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).