public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33738] -Wtype-limits misses a warning when comparing enums
Date: Tue, 13 Nov 2007 04:56:00 -0000 [thread overview]
Message-ID: <20071113045556.30266.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33738-91@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from manu at gcc dot gnu dot org 2007-11-13 04:55 -------
(In reply to comment #1)
> Warnings from optimizers are semi a no-no. Yes we have them for strict
> aliasing and overflow but I think those cases are a bit weird. This is
> unspecified behavior no matter what and there is no flag to change the behavior
> here.
Well, Wtype-limits is supposed to warn about this and it doesn't. Can we do it
from the front-end? If not, then warning from the middle-end seems the right
thing to do as long as it is not complex/intrusive.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-11-13 04:55:56
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33738
next prev parent reply other threads:[~2007-11-13 4:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 17:50 [Bug c++/33738] New: " dnovillo at gcc dot gnu dot org
2007-10-11 18:09 ` [Bug c++/33738] " pinskia at gcc dot gnu dot org
2007-11-13 4:56 ` manu at gcc dot gnu dot org [this message]
2008-02-05 4:19 ` dnovillo at gcc dot gnu dot org
2008-02-05 4:30 ` dnovillo at gcc dot gnu dot org
2008-02-05 10:19 ` rguenth at gcc dot gnu dot org
2008-02-05 11:22 ` manu at gcc dot gnu dot org
2008-02-05 16:16 ` dnovillo at google dot com
2008-02-05 16:32 ` dnovillo at gcc dot gnu dot org
2008-02-05 19:54 ` reichelt at gcc dot gnu dot org
2008-02-05 19:57 ` manu at gcc dot gnu dot org
2008-02-05 19:59 ` pinskia at gcc dot gnu dot org
2008-02-24 16:42 ` dnovillo at gcc dot gnu dot org
2008-03-11 5:56 ` dnovillo at gcc dot gnu dot org
2008-12-29 6:11 ` pinskia 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=20071113045556.30266.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: 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).