public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49615] internal compiler error: verify_stmts failed / LHS in noreturn call with pointer-to-never-returning-member
Date: Sat, 02 Jul 2011 20:36:00 -0000 [thread overview]
Message-ID: <bug-49615-4-NFoklwKHJQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49615-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49615
--- Comment #1 from Harald van Dijk <harald at gigawatt dot nl> 2011-07-02 20:35:39 UTC ---
Actually, I'll include the other slightly different testcase here, since it'll
probably be the same problem. If you prefer me reporting it as a separate bug,
I will do so.
$ cat bug.ii
template <class T>
static inline bool Dispatch (T* obj, void (T::*func) ())
{
(obj->*func) ();
}
class C
{
bool f (int);
void g ();
};
bool C::f (int n)
{
bool b;
switch (n)
{
case 0:
b = Dispatch (this, &C::g);
case 1:
b = Dispatch (this, &C::g);
}
}
void C::g ()
{
for (;;) { }
}
$ gcc -c -O bug.ii # works
$ gcc -c -O bug.ii -g
bug.ii: In member function ‘bool C::f(int)’:
bug.ii:11:6: error: control flow in the middle of basic block 4
bug.ii:11:6: internal compiler error: verify_flow_info failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2011-07-02 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 20:30 [Bug c++/49615] New: " harald at gigawatt dot nl
2011-07-02 20:36 ` harald at gigawatt dot nl [this message]
2011-07-04 9:58 ` [Bug tree-optimization/49615] [4.6 Regression] " rguenth at gcc dot gnu.org
2011-07-04 9:58 ` [Bug c++/49615] " rguenth at gcc dot gnu.org
2011-07-04 10:05 ` [Bug tree-optimization/49615] [4.6 Regression] " hubicka at ucw dot cz
2011-07-04 10:38 ` rguenther at suse dot de
2011-07-04 12:07 ` rguenth at gcc dot gnu.org
2011-07-04 12:09 ` rguenth at gcc dot gnu.org
2011-07-04 12:19 ` rguenth at gcc dot gnu.org
2011-07-04 12:23 ` rguenth at gcc dot gnu.org
2011-07-04 12:24 ` rguenth at gcc dot gnu.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=bug-49615-4-NFoklwKHJQ@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).