From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
martin jambor <mjambor@suse.cz>,
Richard Guenther <rguenther@suse.de>
Subject: Re: [RFC] Context sensitive inline analysis
Date: Wed, 27 Apr 2011 14:38:00 -0000 [thread overview]
Message-ID: <BANLkTi=YjTQgEM9=RJX8amgZkEdSWXNEUQ@mail.gmail.com> (raw)
In-Reply-To: <20110427121610.GA1981@kam.mff.cuni.cz>
On Wed, Apr 27, 2011 at 5:16 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
> Hi,
> I don't really have testcase for the HP nor AIX ICE, however I can reproduce same ICE when I hack x86 to
> not use ctors/dtors. This patch fixes it - the problem is that ipa-prop ignore newly added functions
> (the global ctor built) while ipa-inline not and ipa-inline does use ipa-prop for its analysis.
> Fixed by adding the corresponding hook to ipa-prop, regstested&bootstrapped x86_64-linux with the
> hack and comitted. Let me know if it fixes your problem or not.
>
> Honza
>
> * ipa-prop.c (function_insertion_hook_holder): New holder.
> (ipa_add_new_function): New function.
> (ipa_register_cgraph_hooks, ipa_unregister_cgraph_hooks): Register/deregister
> holder.
This may have caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48791
--
H.J.
next prev parent reply other threads:[~2011-04-27 14:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 15:35 David Edelsohn
2011-04-26 13:02 ` Jan Hubicka
2011-04-27 13:18 ` Jan Hubicka
2011-04-27 14:38 ` H.J. Lu [this message]
2011-04-27 15:46 ` Jan Hubicka
2011-04-28 13:27 ` David Edelsohn
2011-04-28 13:43 ` Jan Hubicka
[not found] ` <BANLkTikScRy+QwZiPyGhHhmuu+ACF65HJA@mail.gmail.com>
2011-04-30 13:38 ` Jan Hubicka
2011-04-30 16:38 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2011-04-22 14:17 Jan Hubicka
2011-04-22 21:02 ` Jan Hubicka
2011-04-23 0:14 ` Jan Hubicka
2011-04-23 10:47 ` Richard Guenther
2011-04-23 17:00 ` Jan Hubicka
2011-05-27 8:31 ` H.J. Lu
2011-05-27 8:52 ` H.J. Lu
2011-09-27 16:20 ` Jan Hubicka
2011-09-28 11:56 ` Richard Sandiford
2011-10-03 8:12 ` Richard Sandiford
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='BANLkTi=YjTQgEM9=RJX8amgZkEdSWXNEUQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
--cc=rguenther@suse.de \
/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).