public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53132] Missing top level in diagnostic's instantiation stack Date: Fri, 19 Dec 2014 16:26:00 -0000 [thread overview] Message-ID: <bug-53132-4-89NYjQlVdR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53132-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53132 --- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Paolo Carlini from comment #4) > Manuel, shall we close this? If there is no self-contained reproducible testcase forthcoming, I would say yes. >From gcc-bugs-return-471410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 19 16:37:06 2014 Return-Path: <gcc-bugs-return-471410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 11323 invoked by alias); 19 Dec 2014 16:37:05 -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 11263 invoked by uid 48); 19 Dec 2014 16:37:00 -0000 From: "gcc at breakpoint dot cc" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/64294] invalid code, zero check gets optimized away Date: Fri, 19 Dec 2014 16:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at breakpoint dot cc X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_known_to_work Message-ID: <bug-64294-4-SkCDPegZHw@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64294-4@http.gcc.gnu.org/bugzilla/> References: <bug-64294-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: 2014-12/txt/msg02417.txt.bz2 Content-length: 520 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd294 Sebastian Andrzej Siewior <gcc at breakpoint dot cc> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.7.2 --- Comment #6 from Sebastian Andrzej Siewior <gcc at breakpoint dot cc> --- I just reprduced this on arm-linux-gnueabi. Unless there is something wrong with the code, this isn't x86 specific as the Target suggests.
next prev parent reply other threads:[~2014-12-19 16:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-26 23:12 [Bug c++/53132] New: " jyasskin at gcc dot gnu.org 2012-05-21 17:48 ` [Bug c++/53132] " paolo.carlini at oracle dot com 2012-05-21 19:31 ` manu at gcc dot gnu.org 2014-11-20 16:50 ` paolo.carlini at oracle dot com 2014-12-19 16:13 ` paolo.carlini at oracle dot com 2014-12-19 16:26 ` manu at gcc dot gnu.org [this message] 2014-12-19 17:25 ` paolo.carlini at oracle dot com 2015-07-28 9:37 ` paolo.carlini at oracle 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-53132-4-89NYjQlVdR@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).