public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/59893] Use LTO for libgcc.a, libstdc++.a, etc
Date: Tue, 21 Jan 2014 02:02:00 -0000 [thread overview]
Message-ID: <bug-59893-4-YQYAkBXf2B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59893-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59893
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Mon, 20 Jan 2014, glisse at gcc dot gnu.org wrote:
> LTO is not really a brand new, experimental and exotic option anymore. I
> believe that by default, on systems that support it, we should build the static
> target libraries that are part of gcc with -flto (and obviously
> -ffat-lto-objects). This should have no impact on people not using LTO (well,
Are LTO objects now independent of the compiler host (see bug 41526) (so
that such libraries will work properly when copied from one host to
another as part of a Canadian cross build)?
next parent reply other threads:[~2014-01-21 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-59893-4@http.gcc.gnu.org/bugzilla/>
2014-01-21 2:02 ` joseph at codesourcery dot com [this message]
2014-01-21 6:19 ` glisse at gcc dot gnu.org
2014-01-21 19:06 ` glisse at gcc dot gnu.org
2014-01-22 22:16 ` glisse at gcc dot gnu.org
2014-01-29 10:09 ` rguenth at gcc dot gnu.org
2014-02-12 16:26 ` d.g.gorbachev at gmail dot com
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=bug-59893-4-YQYAkBXf2B@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).