public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/37038] Bogus warning from GCC Date: Sun, 10 Aug 2008 20:32:00 -0000 [thread overview] Message-ID: <20080810203047.12607.qmail@sourceware.org> (raw) In-Reply-To: <bug-37038-15321@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from sam at gcc dot gnu dot org 2008-08-10 20:30 ------- Subject: Re: Bogus warning from GCC >> The warning is likely to come from tree-vrp.c. > The only place which emits this warning is from c-common.c so I > think someone needs to debug this a little bit. Place a breakpoint > on warning and then look at the backtrace to figure out where the > warning is coming from. If it is truly coming from c-common.c, then > the Ada front-end is wrong to include that source at all. As I wrote, it must be coming from tree-vrp.c: the warning message is split on two lines there, which is why I didn't catch it either the first time I looked for it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37038
next prev parent reply other threads:[~2008-08-10 20:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-06 14:49 [Bug ada/37038] New: " sam at gcc dot gnu dot org 2008-08-06 14:50 ` [Bug ada/37038] " sam at gcc dot gnu dot org 2008-08-06 15:40 ` sam at gcc dot gnu dot org 2008-08-06 15:46 ` Andrew Thomas Pinski 2008-08-06 15:47 ` pinskia at gmail dot com 2008-08-06 16:58 ` sam at gcc dot gnu dot org 2008-08-10 20:18 ` pinskia at gcc dot gnu dot org 2008-08-10 20:32 ` sam at gcc dot gnu dot org [this message] 2008-08-10 20:36 ` pinskia at gcc dot gnu dot org 2008-08-10 20:36 ` pinskia at gcc dot gnu dot org 2009-10-06 11:37 ` sam at gcc dot gnu dot org 2009-10-06 11:37 ` sam 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=20080810203047.12607.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).