public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61654] [4.9/4.10 Regression] ICE in release_function_body, at cgraph.c:1699
Date: Mon, 07 Jul 2014 11:38:00 -0000	[thread overview]
Message-ID: <bug-61654-4-w41IjOhqjS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61654-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61654

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Richard mentioned that #c7 doesn't ICE on the 4.9 branch, only trunk.  This one
ICEs on the 4.9 branch too (the only change is " = 0", i.e. making A::a pure
virtual), again -O3 -m32 is needed:

struct A
{
  virtual int a (int, int = 0) = 0;
  void b ();
  void c ();
  int d;
};

struct B : virtual A
{
  int a (int, int);
  int e;
};

int f;

void
A::b ()
{
  a (0);
}

void
A::c ()
{
  a (f);
}

int
B::a (int, int)
{
  return e;
}


  parent reply	other threads:[~2014-07-07 11:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  6:48 [Bug c++/61654] New: [4.9.1] " manuel.lauss at googlemail dot com
2014-06-30  7:05 ` [Bug middle-end/61654] [4.9/4.10 Regression] " trippels at gcc dot gnu.org
2014-06-30  7:19 ` trippels at gcc dot gnu.org
2014-07-03 13:59 ` jakub at gcc dot gnu.org
2014-07-04  8:39 ` jakub at gcc dot gnu.org
2014-07-04  8:40 ` jakub at gcc dot gnu.org
2014-07-04  9:16 ` jakub at gcc dot gnu.org
2014-07-07 11:06 ` rguenth at gcc dot gnu.org
2014-07-07 11:07 ` rguenth at gcc dot gnu.org
2014-07-07 11:38 ` jakub at gcc dot gnu.org [this message]
2014-07-16 13:27 ` jakub at gcc dot gnu.org
2014-07-24 15:17 ` jamborm at gcc dot gnu.org
2014-09-03  8:48 ` [Bug middle-end/61654] [4.9/5 " jamborm at gcc dot gnu.org
2014-09-10 11:34 ` jamborm at gcc dot gnu.org
2014-09-12 16:53 ` jamborm at gcc dot gnu.org
2014-09-12 16:53 ` jamborm 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-61654-4-w41IjOhqjS@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).