From: Uros Bizjak <ubizjak@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, bootstrap]: Add bootstrap-lto-noplugin build configuration (PR65537)
Date: Thu, 26 Mar 2015 08:20:00 -0000 [thread overview]
Message-ID: <CAFULd4YS04jH78tC9njvfaGJ9Y7kcXdPm=o959cWPZwAxe-75w@mail.gmail.com> (raw)
In-Reply-To: <20150326011148.GD8802@atrey.karlin.mff.cuni.cz>
On Thu, Mar 26, 2015 at 2:11 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
>> Hello!
>>
>> Attached patch introduces bootstrap-lto-noplugin bootstrap
>> configuration for hosts that do not support linker plugin (e.g. CentOS
>> 5.11 with binutils 2.17). Also, the patch adds some additional
>> documentation to bootstrap-lto option.
[...]
> Can you, please, add a note that without linker plugin the static libraries are
> not compiled with linktime optimization. Because GCC middle-end and backend is
> in libbackend.a it means that only (part of) the frontend is actually LTO
> optimized?
Thanks, I have added following text to the description:
--cut here--
@item @samp{bootstrap-lto-noplugin}
This option is similar to @code{bootstrap-lto}, but is intended for
-hosts that do not support the linker plugin.
+hosts that do not support the linker plugin. Please note that static
+libraries are not compiled with link time optimizations without
+linker plugin. Since GCC middle-end and back-end are in libbackend.a,
+it means that only part of the frontend is actually LTO optimized.
--cut here--
Uros.
next prev parent reply other threads:[~2015-03-26 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:43 Uros Bizjak
2015-03-25 14:24 ` Jakub Jelinek
2015-03-25 19:16 ` Uros Bizjak
2015-03-26 1:11 ` Jan Hubicka
2015-03-26 8:20 ` Uros Bizjak [this message]
2015-04-06 12:45 ` Gerald Pfeifer
2015-04-06 17:19 ` Sandra Loosemore
2015-04-08 12:13 ` Gerald Pfeifer
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='CAFULd4YS04jH78tC9njvfaGJ9Y7kcXdPm=o959cWPZwAxe-75w@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.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).