public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49772] [4.7 Regression] ICE: in ipa_pta_execute, at tree-ssa-structalias.c:6790 with -fipa-pta
Date: Thu, 04 Aug 2011 09:21:00 -0000	[thread overview]
Message-ID: <bug-49772-4-ffonkNCRsN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49772-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> 2011-08-04 09:20:21 UTC ---
On Wed, 3 Aug 2011, hubicka at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49772
> 
> --- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-08-03 19:57:06 UTC ---
> Hmm, we should never make the cgrpah point to inline variant in this case, so
> rest of compilation should go smoothly after the error is output. I don't think
> it is what is confusing ipa-pta, especially now when it is run after inlining?

What happens is that in expand_call_inline we fail the inlining via
an error, but at this point of course the edge points to the inline
clone and that stays so.

I suppose when expand_call_inline fails we have to re-direct the
edge to the original function (huh, eventually make sure it is not
optimized away as well).

Or, finally, _never_ fail that late

Richard.


  parent reply	other threads:[~2011-08-04  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 21:04 [Bug tree-optimization/49772] New: " zsojka at seznam dot cz
2011-07-17 21:06 ` [Bug tree-optimization/49772] " zsojka at seznam dot cz
2011-07-18  8:28 ` rguenth at gcc dot gnu.org
2011-08-03 19:57 ` hubicka at gcc dot gnu.org
2011-08-04  9:21 ` rguenther at suse dot de [this message]
2011-08-04 18:33 ` hubicka at ucw dot cz
2011-10-27  9:45 ` rguenth at gcc dot gnu.org
2011-12-06 10:38 ` rguenth at gcc dot gnu.org
2011-12-07  5:36 ` zsojka at seznam dot cz
2011-12-07  5:37 ` zsojka at seznam dot cz
2011-12-08  4:55 ` pinskia at gcc dot gnu.org
2011-12-08  9:05 ` rguenther at suse dot de
2011-12-08 11:45 ` rguenth at gcc dot gnu.org
2011-12-08 13:26 ` rguenth at gcc dot gnu.org
2011-12-08 13:34 ` 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-49772-4-ffonkNCRsN@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).