public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54329] [4.8 Regression] gcc/cfgcleanup.o differs
Date: Mon, 19 Nov 2012 14:37:00 -0000 [thread overview]
Message-ID: <bug-54329-4-n4X07Mbb2u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54329-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54329
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-11-19
CC| |jakub at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-19 14:36:53 UTC ---
Can you still reproduce it? Are you using stock trunk, not some extra patches
on top of it? If you rebuild the source file which failed checksum checking
with the options passed to g++ normally to compile it plus -fcompare-debug,
does it fail with an -fcompare-debug failure? If yes, please attach the
preprocessed source of it and all command line options.
next prev parent reply other threads:[~2012-11-19 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 11:19 [Bug bootstrap/54329] New: gcc/reginfo.o differs wbrana at gmail dot com
2012-08-20 11:20 ` [Bug bootstrap/54329] " wbrana at gmail dot com
2012-08-20 11:42 ` rguenth at gcc dot gnu.org
2012-08-20 12:04 ` wbrana at gmail dot com
2012-08-27 8:28 ` wbrana at gmail dot com
2012-09-10 7:45 ` wbrana at gmail dot com
2012-09-10 7:47 ` [Bug bootstrap/54329] gcc/cfgcleanup.o differs wbrana at gmail dot com
2012-09-24 11:49 ` [Bug bootstrap/54329] [4.8 Regression] " wbrana at gmail dot com
2012-11-19 14:37 ` jakub at gcc dot gnu.org [this message]
2012-11-20 18:44 ` wbrana at gmail dot com
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=bug-54329-4-n4X07Mbb2u@http.gcc.gnu.org/bugzilla/ \
--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).