public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/37038] Bogus warning from GCC Date: Wed, 06 Aug 2008 15:47:00 -0000 [thread overview] Message-ID: <20080806154611.12467.qmail@sourceware.org> (raw) In-Reply-To: <bug-37038-15321@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gmail dot com 2008-08-06 15:46 ------- Subject: Re: Bogus warning from GCC Sent from my iPhone On Aug 6, 2008, at 8:39, "sam at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org > wrote: > > > ------- Comment #2 from sam at gcc dot gnu dot org 2008-08-06 15:39 > ------- > The warning comes from a range check which is emitted by Gigi. The > backend > knows that this check is useless, and warns about it. As far as I > can tell, > there is no way to suppress the warning in shorten_compare (c- > common.c), except > by setting a global option (OPT_Wtype_limits) to false. C-common.c being included by the Ada front-end???? That is a c front- end file. -- Pinski > > > > -- > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37038 > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37038
next prev parent reply other threads:[~2008-08-06 15:47 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 [this message] 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 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=20080806154611.12467.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).