From: Diego Novillo <dnovillo@google.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org, Fortran List <fortran@gcc.gnu.org>
Subject: Re: [LTO merge][0/15] Description of the final 15 patches
Date: Tue, 29 Sep 2009 13:06:00 -0000 [thread overview]
Message-ID: <b798aad50909290606m6c3fd98bpd8cc0b81dcb30f38@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909290155280.1054@digraph.polyomino.org.uk>
On Mon, Sep 28, 2009 at 22:00, Joseph S. Myers <joseph@codesourcery.com> wrote:
> You say "tested on x86_64". More detail is needed. Have you tested both
Sorry, I completely spaced out and forgot to mention this. Various
folks are testing the branch. I sent a request for testing the branch
(http://gcc.gnu.org/ml/gcc/2009-09/msg00566.html). I'm using that
thread to keep track of breakage that should be fixed before the final
merge.
> LTO-enabled and LTO-disabled configurations, making sure there are no
> regressions in each case?
Yes. Targets with no ELF support refuse to enable LTO and error out
at configure time if --enable-lto is forced. There was a bug in some
of the testsuite patches that Richi fixed.
Diego.
prev parent reply other threads:[~2009-09-29 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 0:58 Diego Novillo
2009-09-29 2:03 ` Joseph S. Myers
2009-09-29 14:48 ` Ian Lance Taylor
2009-09-29 14:56 ` Diego Novillo
2009-09-29 16:45 ` Paolo Bonzini
2009-09-29 16:53 ` Ian Lance Taylor
2009-09-29 16:56 ` Paolo Bonzini
2009-09-29 18:54 ` Ian Lance Taylor
2009-09-29 2:07 ` Joseph S. Myers
2009-09-29 13:06 ` Diego Novillo [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=b798aad50909290606m6c3fd98bpd8cc0b81dcb30f38@mail.gmail.com \
--to=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).