public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrakov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39259]  New: internal compiler error: in initialize_cfun, at tree-inline.c:1749
Date: Sat, 21 Feb 2009 17:39:00 -0000	[thread overview]
Message-ID: <bug-39259-16726@http.gcc.gnu.org/bugzilla/> (raw)

This meaningless testcase (reduced by delta from the real program), when
compiled with g++ 4.4 (but not 4.3), produces an ICE.

extern "C" int __mysetjmp () __attribute__ ((__returns_twice__));

class TContStatus {};

class TContEvent
{
public:
  inline void Execute () throw();
};

class TCont
{
public:
  TContStatus ReadD (void* buf, int deadline)
  {
    TContEvent event;
    event.Execute ();
    return TContStatus();
  }
  TContStatus ReadI (void *buf)
  {
    return ReadD (buf, 1);
  }
};

void TContEvent::Execute () throw ()
{
  __mysetjmp();
}

void Broken (TCont *mCont)
{
  mCont->ReadI(0);
  mCont->ReadI(0);
}


-- 
           Summary: internal compiler error: in initialize_cfun, at tree-
                    inline.c:1749
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: patrakov at gmail dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2009-02-21 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 17:39 patrakov at gmail dot com [this message]
2009-02-21 17:57 ` [Bug tree-optimization/39259] [4.4 Regression] " rguenth at gcc dot gnu dot org
2009-02-21 19:58 ` hjl dot tools at gmail dot com
2009-02-21 20:04 ` hjl dot tools at gmail dot com
2009-02-21 20:22 ` hjl dot tools at gmail dot com
2009-02-23 14:09 ` jamborm at gcc dot gnu dot org
2009-02-23 15:05 ` jh at suse dot cz
2009-02-24 13:44 ` jamborm at gcc dot gnu dot org
2009-02-25 18:20 ` jamborm 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=bug-39259-16726@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).