public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33589] [4.3 regression] ICE on valid code at -O2: verify_flow_info failed
Date: Tue, 23 Oct 2007 06:53:00 -0000	[thread overview]
Message-ID: <20071023065327.32511.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33589-14817@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pinskia at gcc dot gnu dot org  2007-10-23 06:53 -------
Here is a "semi" undefined case which shows the same issue:
void f(void*) throw();

void somefunction()
{
try {
   void (*g)(void*) = (void (*)(void*))f;
   void (*g2)(int*) = (void (*)(int*))g;
    g2(0);
} catch (...)
{throw;}
}


----------- CUT -----
Janis could you do a regression hunt on this bug with the new testcase?


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janis at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33589


  parent reply	other threads:[~2007-10-23  6:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29 17:56 [Bug c++/33589] New: " a dot chavasse at gmail dot com
2007-09-29 19:05 ` [Bug middle-end/33589] " rguenth at gcc dot gnu dot org
2007-10-10 18:06 ` mmitchel at gcc dot gnu dot org
2007-10-19 16:37 ` janis at gcc dot gnu dot org
2007-10-23  6:10 ` pinskia at gcc dot gnu dot org
2007-10-23  6:39 ` pinskia at gcc dot gnu dot org
2007-10-23  6:53 ` pinskia at gcc dot gnu dot org [this message]
2007-10-28  1:11 ` pinskia at gcc dot gnu dot org
2007-10-28  1:18 ` pinskia at gcc dot gnu dot org
2007-10-28 17:01 ` pinskia at gcc dot gnu dot org
2007-10-28 17:02 ` 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=20071023065327.32511.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).