public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Devirtualization dump functions fix
Date: Fri, 27 Jun 2014 08:38:00 -0000	[thread overview]
Message-ID: <CAFiYyc35WCVf-gVBwjc88nwmWZ0KBnWhRjJyGSi-r5bSR_KGsA@mail.gmail.com> (raw)
In-Reply-To: <53AC4337.4050205@suse.cz>

On Thu, Jun 26, 2014 at 5:58 PM, Martin Liška <mliska@suse.cz> wrote:
>
> On 06/26/2014 04:29 PM, Jakub Jelinek wrote:
>>
>> On Thu, Jun 26, 2014 at 04:27:49PM +0200, Martin Liška wrote:
>>>>>
>>>>> Well yes - it is of course similar broken in spirit but at least a lot
>>>>> simpler ;)  I'd put a comment there why we do check g for NULL.
>>>>
>>>> But it increases overhead, there are hundreds of gimple_location calls
>>>> and most of them will never pass NULL.  Can't you simply
>>>> do what you do in the inline here in the couple of spots where
>>>> the stmt might be NULL?
>>>
>>> Sure, do you have any suggestion how should be called such function?
>>> Suggestion: gimple_location_or_unknown ?
>>
>> gimple_location_safe or gimple_safe_location?
>>
>>         Jakub
>
> Thanks, there's new patch.
>
> Patch has been tested for Firefox with -flto -fdump-ipa-devirt.
> Bootstrap and regression tests have been running.
>
> Ready for trunk after regression tests?

Ok with s/gimple_safe_location/gimple_location_safe/ (I think that's
the more canonical naming - what's a "safe location" after all?)

Thanks,
Richard.

>
> ChangeLog:
>
> 2014-06-26  Martin Liska  <mliska@suse.cz>
>
>     * gimple.h (gimple_safe_location): New function introduced.
>     * cgraphunit.c (walk_polymorphic_call_targets): Usage
>     of gimple_safe_location replaces gimple_location.
>     (gimple_fold_call): Likewise.
>     * ipa-devirt.c (ipa_devirt): Likewise.
>     * ipa-prop.c (ipa_make_edge_direct_to_target): Likewise.
>     * ipa.c (walk_polymorphic_call_targets): Likewise.
>     * tree-ssa-pre.c (eliminate_dom_walker::before_dom_children): Likewise.

  reply	other threads:[~2014-06-27  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 13:01 Martin Liška
2014-06-26 13:20 ` Richard Biener
2014-06-26 13:43   ` Martin Liška
2014-06-26 14:11     ` Richard Biener
2014-06-26 14:19       ` Jakub Jelinek
2014-06-26 14:27         ` Martin Liška
2014-06-26 14:29           ` Jakub Jelinek
2014-06-26 15:58             ` Martin Liška
2014-06-27  8:38               ` Richard Biener [this message]
2014-06-27  9:25                 ` Martin Liška

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=CAFiYyc35WCVf-gVBwjc88nwmWZ0KBnWhRjJyGSi-r5bSR_KGsA@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    /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).