public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.org>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: Trunk is closed for LTO merge
Date: Sat, 03 Oct 2009 14:30:00 -0000	[thread overview]
Message-ID: <4AC75FE9.3070503@moene.org> (raw)
In-Reply-To: <b798aad50910030719p24a4f40bt92f8365a9b39aa@mail.gmail.com>

Diego Novillo wrote:

> On Sat, Oct 3, 2009 at 10:13, Toon Moene <toon@moene.org> wrote:
> 
>> Will the merge allow lto by default (so that we do not have to specify
>> --enable-lto) ?
> 
> If the correct version is found, yes.  This is the same behaviour that
> is implemented in the lto branch.
> 
>> Or do we have to force it, like on the branch ?

[ Never had to force it on the branch, either ]

OK,

So tomorrow I plan to svn up my gcc trunk, recompile it for C and 
Fortran, recompile our Weather Forecasting system with it, and see what 
happens (the compile of the Weather code doesn't use -flto yet, obviously.

Thanks,

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html

  reply	other threads:[~2009-10-03 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 11:39 Diego Novillo
2009-10-03 14:13 ` Toon Moene
2009-10-03 14:19   ` Diego Novillo
2009-10-03 14:30     ` Toon Moene [this message]
2009-10-03 14:34       ` Diego Novillo
2009-10-03 14:44         ` Richard Guenther
2009-10-03 14:45           ` Diego Novillo
2009-10-04 16:58       ` Toon Moene

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=4AC75FE9.3070503@moene.org \
    --to=toon@moene.org \
    --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).