From: fche@redhat.com (Frank Ch. Eigler)
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, fortran@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: LTO branch merged into trunk - trunk remains CLOSED
Date: Mon, 05 Oct 2009 14:42:00 -0000 [thread overview]
Message-ID: <y0mskdxj41u.fsf@fche.csb> (raw)
In-Reply-To: <20091003211217.GA22755@google.com> (Diego Novillo's message of "Sat, 3 Oct 2009 17:12:17 -0400")
Diego Novillo <dnovillo@google.com> writes:
> The LTO branch has been merged into trunk at revision 152434.
> [...]
Congrats.
> [...] That's it. The result should, in principle, execute faster
> but our IPA cost models are still not tweaked for LTO. We've seen
> speedups as well as slowdowns in benchmarks (see the LTO testers at
> http://gcc.opensuse.org/). [...]
Would it make sense to keep -flto unemphasized in NEWS etc., until
some consistently positive performance results of some sort have been
identified?
- FChE
prev parent reply other threads:[~2009-10-05 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 21:12 Diego Novillo
2009-10-03 21:33 ` Richard Guenther
2009-10-03 21:36 ` Diego Novillo
2009-10-03 22:31 ` Richard Guenther
2009-10-03 23:40 ` Diego Novillo
2009-10-04 1:05 ` Diego Novillo
2009-10-05 14:42 ` Frank Ch. Eigler [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=y0mskdxj41u.fsf@fche.csb \
--to=fche@redhat.com \
--cc=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@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).