public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/41862] [4.5 Regression] -fgcse-sm causes bootstrap comparison failures
Date: Fri, 27 Nov 2009 11:23:00 -0000	[thread overview]
Message-ID: <20091127112321.31655.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41862-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from zsojka at seznam dot cz  2009-11-27 11:23 -------
My fault for not using -fgcse-sm in BOOT_CFLAGS. With that, it gets worse:
$ nice -n 19 make -j3 BOOT_CFLAGS="-O2 -fgcse-sm"

Comparing stages 2 and 3
warning: gcc/cc1plus-checksum.o differs
warning: gcc/cc1-checksum.o differs
Bootstrap comparison failure!
gcc/cp/pt.o differs
gcc/explow.o differs
gcc/tree-into-ssa.o differs
gcc/bitmap.o differs
gcc/dwarf2out.o differs
gcc/double-int.o differs
gcc/ipa-prop.o differs
gcc/stor-layout.o differs
libdecnumber/decimal128.o differs
libdecnumber/decimal32.o differs
libdecnumber/decimal64.o differs
libdecnumber/decNumber.o differs
x86_64-unknown-linux-gnu/32/libgcc/trunctfxf2_s.o differs
x86_64-unknown-linux-gnu/32/libgcc/multf3_s.o differs
x86_64-unknown-linux-gnu/32/libgcc/multf3.o differs
x86_64-unknown-linux-gnu/32/libgcc/fixtfsi_s.o differs
x86_64-unknown-linux-gnu/32/libgcc/bid128_div.o differs


-- 

zsojka at seznam dot cz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|valgrind warns about using  |[4.5 Regression] -fgcse-sm
                   |uninitialized variable with |causes bootstrap comparison
                   |-fgcse-sm                   |failures


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41862


  parent reply	other threads:[~2009-11-27 11:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  0:03 [Bug rtl-optimization/41862] New: valgrind warns about using uninitialized variable with -fgcse-sm zsojka at seznam dot cz
2009-10-29  0:04 ` [Bug rtl-optimization/41862] " zsojka at seznam dot cz
2009-10-29  0:06 ` zsojka at seznam dot cz
2009-10-29 10:25 ` rguenth at gcc dot gnu dot org
2009-10-29 10:58 ` steven at gcc dot gnu dot org
2009-11-17 18:34 ` zsojka at seznam dot cz
2009-11-25 10:45 ` zsojka at seznam dot cz
2009-11-27 11:23 ` zsojka at seznam dot cz [this message]
2009-12-04 14:25 ` [Bug rtl-optimization/41862] [4.5 Regression] -fgcse-sm causes bootstrap comparison failures rguenth at gcc dot gnu dot org
2009-12-24 13:12 ` steven at gcc dot gnu dot org
2009-12-24 20:24 ` zsojka at seznam dot cz
2009-12-24 20:35 ` zsojka at seznam dot cz
2010-01-02 15:57 ` rguenth at gcc dot gnu dot org
2010-01-03 17:15 ` steven at gcc dot gnu dot org
2010-01-03 17:23 ` steven at gcc dot gnu dot org
2010-01-03 18:25 ` rguenth at gcc dot gnu dot org
2010-01-03 20:03 ` [Bug rtl-optimization/41862] [4.5 Regression] -fgcse-sm causes bootstrap-debug " steven at gcc dot gnu dot org
2010-01-03 22:33 ` rguenth at gcc dot gnu dot org
2010-01-03 22:42 ` steven at gcc dot gnu dot org
2010-01-03 22:46 ` steven 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=20091127112321.31655.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: link
Be 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).