public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Guenther <rguenther@suse.de>
Subject: Re: Drop target_option_node reconstruction logic.
Date: Wed, 19 Nov 2014 18:44:00 -0000	[thread overview]
Message-ID: <CAMe9rOrrXnqGxHzMvBmHKYDKHRA7Yw6EWVr7avGRmrwkXHgamQ@mail.gmail.com> (raw)
In-Reply-To: <20141119181143.GB3523@kam.mff.cuni.cz>

On Wed, Nov 19, 2014 at 10:11 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
>> On Fri, Nov 14, 2014 at 11:13 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
> nz
>> > Hi,
>> > this patch kills lto's code to rebuilt DECL_FUNCTION_SPECIFIC_TARGET from target
>> > attributes.  This code was never complete and it should be no-op now when we save
>> > tehe target nodes.
>> > It also makes free_land_data_in_decl to actually anotate all function bodies with
>> > a default option node.  The reason is that when LTOint units, one compiled with
>> > default settings and one, say with -msse3, we want ot keep these functions preserved.
>> >
>> > Incrementally i will proceed with similar changes for optimization nodes.
>> >
>> > Bootstrapped/regtested ppc64-linux, earlier version tested at x86_64-linux and
>> > firefox LTO, OK?
>> >
>> > Honza
>> >
>> >         * lto.c (lto_read_decls): Do not rebuild DECL_FUNCTION_SPECIFIC_TARGET.
>> >         * tree.c (free_lang_data_in_decl): Annotate all functio nbodies with
>> >         DECL_FUNCTION_SPECIFIC_TARGET.
>>
>> It caused:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63917
> This one seems to be abou ifcft change by Zhenqiang?
>
> Honza
>>
>> --
>> H.J.

Oops. I meant:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63967
-- 
H.J.

      reply	other threads:[~2014-11-19 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 19:20 Jan Hubicka
2014-11-14 20:07 ` Markus Trippelsdorf
2014-11-14 20:16   ` Jan Hubicka
2014-11-15 11:05 ` Richard Biener
2014-11-19 15:56 ` H.J. Lu
2014-11-19 18:16   ` Jan Hubicka
2014-11-19 18:44     ` H.J. Lu [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=CAMe9rOrrXnqGxHzMvBmHKYDKHRA7Yw6EWVr7avGRmrwkXHgamQ@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.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).