From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix for PR ipa/64146
Date: Tue, 16 Dec 2014 16:30:00 -0000 [thread overview]
Message-ID: <54905866.6070604@suse.cz> (raw)
In-Reply-To: <CAFiYyc0uxQAy819-ptp+=8KG1X-hmzRVZLK2ObcgZoSs9zexjw@mail.gmail.com>
On 12/11/2014 03:03 PM, Richard Biener wrote:
> On Thu, Dec 11, 2014 at 2:49 PM, Martin Liška <mliska@suse.cz> wrote:
>> Hello.
>>
>> In PR64146, for position independent code IPA ICF should be more careful
>> about thunk creation.
>> Patch can bootstrap on x86_64-linux-pc and no new regression was seen.
>>
>> Ready for thunk?
>
> Hmm, does that merge the functions but
> keep a call to the original alias which can be overridden at runtime?
>
> If so, ok.
Hello.
No, in this case there's no merge operation processed.
Function are going to remain as they are.
I hope such behavior is the right one.
Martin
>
> Thanks,
> Richard.
>
>> Thank you,
>> Martin
next prev parent reply other threads:[~2014-12-16 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:49 Martin Liška
2014-12-11 14:03 ` Richard Biener
2014-12-16 16:30 ` Martin Liška [this message]
2014-12-17 14:49 ` Richard Biener
2014-12-12 17:21 Dominique Dhumieres
2014-12-16 16:04 ` 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=54905866.6070604@suse.cz \
--to=mliska@suse.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).