From: Jan Hubicka <hubicka@ucw.cz>
To: GCC Patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH, PR 48613] Don't stream jump functions if there are none
Date: Tue, 14 Jun 2011 22:46:00 -0000 [thread overview]
Message-ID: <20110614223841.GE11211@kam.mff.cuni.cz> (raw)
In-Reply-To: <20110614205103.GB30874@virgil.arch.suse.de>
> Hi,
>
> the patch below fixes PR 48613 which is an ICE with -O0
> -findirect-inlining. Rather than adding "&& optimize" here and there,
> at this place we can easily see whether there is something to do or
> not by testing ipa_node_params_vector for NULL. And the
> flag-triggering combinations can -and are - dealt elsewhere.
>
> Bootstrapped and tested on trunk on x86_64-linux. OK for trunk and
> subsequently for the 4.6 branch too?
>
> Thanks,
>
> Martin
>
> 2011-06-13 Martin Jambor <mjambor@suse.cz>
>
> PR tree-optimization/48613
> * ipa-prop.c (ipa_prop_write_jump_functions): Return immediately if
> ipa_node_params_vector is NULL.
OK,
thanks!
Honza
prev parent reply other threads:[~2011-06-14 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 20:53 Martin Jambor
2011-06-14 22:46 ` Jan Hubicka [this message]
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=20110614223841.GE11211@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@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).