From: Richard Guenther <richard.guenther@gmail.com>
To: Diego Novillo <dnovillo@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/3] Implement -flto-slim
Date: Tue, 02 Nov 2010 11:06:00 -0000 [thread overview]
Message-ID: <AANLkTim7K+9inRMKd3fYuKOUubaP817CNK_eB90WjUxx@mail.gmail.com> (raw)
In-Reply-To: <4CCFEF92.4030204@google.com>
On Tue, Nov 2, 2010 at 12:01 PM, Diego Novillo <dnovillo@google.com> wrote:
> On 10-10-16 11:09 , Andi Kleen wrote:
>
>> +@item -flto-slim
>> +Only generate LTO output, no assembler. The result is that the assembler
>> +code is only generated once for a LTO build. This flag is ignored for the
>> LTO
>> +frontend. Will only work with the @option{-fuse-linker-plugin} and
>> +with the @command{gold} linker.
>
> s/Will only/This option will only/
>
> The patch looks fine, but the option is currently not tested. Could you add
> it to LTO_OPTIONS in testsuite/lib/lto.exp:lto_init ?
Hm, it won't work without the linker plugin, will it? So it's not that easy.
Richard.
>
> Diego.
>
next prev parent reply other threads:[~2010-11-02 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 15:09 Updated slim-lto patchkit Andi Kleen
2010-10-16 16:07 ` [PATCH 1/3] Add native ELF and LTO support in collect2 Andi Kleen
2010-10-16 15:09 ` [PATCH 2/3] Implement -flto-slim Andi Kleen
2010-10-16 16:25 ` [PATCH 3/3] Add bootstrap-lto-slim build config Andi Kleen
2010-11-02 11:03 ` [PATCH 2/3] Implement -flto-slim Diego Novillo
2010-11-02 11:06 ` Richard Guenther [this message]
2010-11-02 11:18 ` Diego Novillo
2010-11-02 11:50 ` Andi Kleen
2010-11-02 11:57 ` Richard Guenther
2010-11-02 11:06 ` [PATCH 1/3] Add native ELF and LTO support in collect2 Diego Novillo
2010-11-02 11:07 ` Richard Guenther
2010-11-02 11:41 ` Andi Kleen
2010-11-02 21:26 ` Dave Korn
2010-11-02 11:42 ` Andi Kleen
2010-10-20 21:27 ` *PING* Re: Updated slim-lto patchkit Andi Kleen
2010-10-20 21:34 ` Diego Novillo
2010-10-20 23:09 ` Andi Kleen
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=AANLkTim7K+9inRMKd3fYuKOUubaP817CNK_eB90WjUxx@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dnovillo@google.com \
--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).