public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/59279] [4.9 Regression] r205337 breaks bootstrap with java Date: Sun, 24 Nov 2013 22:40:00 -0000 [thread overview] Message-ID: <bug-59279-4-k9VStLvlYS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59279-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59279 --- Comment #4 from Steven Bosscher <steven at gcc dot gnu.org> --- (In reply to H.J. Lu from comment #1) > When profiledbootstrap configured with > > --with-build-config=bootstrap-lto --disable-werror > > I got > > ../../src-trunk/libiberty/cp-demangle.c: In function âd_demangle_callbackâ: > ../../src-trunk/libiberty/cp-demangle.c:5694:1: error: missing barrier after > block 28 Can you please add the preprocessed source and complete command line for this error? >From gcc-bugs-return-435722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 22:48:23 2013 Return-Path: <gcc-bugs-return-435722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8990 invoked by alias); 24 Nov 2013 22:48:23 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 8959 invoked by uid 48); 24 Nov 2013 22:48:19 -0000 From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/59226] [4.9 Regression] ICE: in record_target_from_binfo, at ipa-devirt.c:661 Date: Sun, 24 Nov 2013 22:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: reichelt at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc cf_known_to_work everconfirmed cf_known_to_fail Message-ID: <bug-59226-4-arWKQDk30X@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59226-4@http.gcc.gnu.org/bugzilla/> References: <bug-59226-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-11/txt/msg02499.txt.bz2 Content-length: 1076 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY226 Volker Reichelt <reichelt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2013-11-24 CC| |reichelt at gcc dot gnu.org Known to work| |4.8.0, 4.8.2 Ever confirmed|0 |1 Known to fail| |4.9.0 --- Comment #1 from Volker Reichelt <reichelt at gcc dot gnu.org> --- Here's a slightly simpler testcase: ================================struct A { virtual void foo() {} }; struct B { virtual void foo() {} }; struct C : virtual A {}; struct D : virtual A, B { virtual void foo() {} }; struct E : C, D { virtual void foo() {} }; void bar(A* p) { p->foo(); } ================================
next prev parent reply other threads:[~2013-11-24 22:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-24 20:39 [Bug bootstrap/59279] New: " hjl.tools at gmail dot com 2013-11-24 20:53 ` [Bug bootstrap/59279] " hjl.tools at gmail dot com 2013-11-24 20:53 ` hjl.tools at gmail dot com 2013-11-24 21:59 ` steven at gcc dot gnu.org 2013-11-24 22:12 ` steven at gcc dot gnu.org 2013-11-24 22:40 ` steven at gcc dot gnu.org [this message] 2013-11-25 8:46 ` steven at gcc dot gnu.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=bug-59279-4-k9VStLvlYS@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: 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).