From: Diego Novillo <dnovillo@google.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: William Maddox <maddox@google.com>,
gcc-patches@gcc.gnu.org,
Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [LTO] Patch to implement -flto-single (-flto-test) switch in gcc driver
Date: Mon, 26 Nov 2007 10:05:00 -0000 [thread overview]
Message-ID: <474A6B7F.1040403@google.com> (raw)
In-Reply-To: <474A19BD.3070401@codesourcery.com>
Mark Mitchell wrote:
> Nathan, I know you've been running the DejaGNU testsuite with LTO. Have
> you been using Bill's patch, or have you cobbled some other mechanism to
> do that?
It's already possible to run most of the testsuite with -flto already.
We've been running compile.exp and execute.exp for a while now. I
patched both files to add -flto a few weeks ago.
There is a fair amount of working tests, which is nice.
Diego.
next prev parent reply other threads:[~2007-11-26 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 15:49 William Maddox
2007-11-26 6:49 ` Mark Mitchell
2007-11-26 10:05 ` Diego Novillo [this message]
2007-11-26 19:00 ` Mark Mitchell
2007-11-26 23:34 ` Diego Novillo
2007-11-27 9:16 ` Mark Mitchell
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=474A6B7F.1040403@google.com \
--to=dnovillo@google.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=maddox@google.com \
--cc=mark@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).