public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "0xd34df00d at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches
Date: Thu, 24 May 2012 20:06:00 -0000 [thread overview]
Message-ID: <bug-53479-4-cs3kZN3vix@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53479
--- Comment #2 from Georg Rudoy <0xd34df00d at gmail dot com> 2012-05-24 20:04:56 UTC ---
(In reply to comment #1)
> Foo f = Foo(2);
> assert( DoFoo( f ) );
>
> Undefined behaviour.
Yes, it is. And isn't it happening at the point of cast of an integer to the
enum class type?
next prev parent reply other threads:[~2012-05-24 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 19:26 [Bug c++/53479] New: Control flow analysis too alarming with switch over an enum class 0xd34df00d at gmail dot com
2012-05-24 19:59 ` [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches redi at gcc dot gnu.org
2012-05-24 20:06 ` 0xd34df00d at gmail dot com [this message]
2012-05-24 20:30 ` redi at gcc dot gnu.org
2012-10-10 19:11 ` 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-53479-4-cs3kZN3vix@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: 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).