From: Andi Kleen <andi@firstfloor.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] Fix -fno-lto (PR lto/46905)
Date: Thu, 16 Dec 2010 18:14:00 -0000 [thread overview]
Message-ID: <20101216165611.GE26663@basil.fritz.box> (raw)
In-Reply-To: <Pine.LNX.4.64.1012161537431.16840@digraph.polyomino.org.uk>
On Thu, Dec 16, 2010 at 03:39:33PM +0000, Joseph S. Myers wrote:
> On Thu, 16 Dec 2010, Richard Guenther wrote:
>
> > > I also tried to do it without opts.c, but setting an 0 initialization
> > > value for the -fno-lto entry, but that didn't work either.
> >
> > Huh, that's strange. Joseph, do you have any idea why? Is it because
> > of how flags get passed to collect2?
>
> Having both flto and fno-lto in common.opt seems dodgy. Try making the
> code in opts.c that handles OPT_flto check "value" (value == 0 meaning
> -fno-lto) instead.
That worked. Here's an updated version. Ok now?
From: Andi Kleen <ak@linux.intel.com>
Date: Wed, 15 Dec 2010 20:10:22 +0100
Subject: [PATCH] Fix -fno-lto (PR lto/46905)
This fixes PR lto/46905.
It's sometimes convenient in large Makefiles to globally enable LTO
in CFLAGS, but disable it again for specific files. The simplest
way to do that is appending -fno-lto, but that didn't work.
Add explicit code to handle this case.
gcc/
2010-12-15 Andi Kleen <ak@linux.intel.com>
PR lto/46905
* collect2.c (main): Handle -fno-lto.
* common.opt (fno-lto): Add.
* opts.c (common_handle_option): Handle OPT_fno_lto.
diff --git a/gcc/collect2.c b/gcc/collect2.c
index 89b21d5..77f794f 100644
--- a/gcc/collect2.c
+++ b/gcc/collect2.c
@@ -1211,6 +1211,8 @@ main (int argc, char **argv)
else if ((! strncmp (argv[i], "-flto=", 6)
|| ! strcmp (argv[i], "-flto")) && ! use_plugin)
lto_mode = LTO_MODE_WHOPR;
+ else if (!strncmp (argv[i], "-fno-lto", 8))
+ lto_mode = LTO_MODE_NONE;
else if (! strcmp (argv[i], "-plugin"))
{
use_plugin = true;
diff --git a/gcc/opts.c b/gcc/opts.c
index 2c8e767..cc4181e 100644
--- a/gcc/opts.c
+++ b/gcc/opts.c
@@ -1670,7 +1670,7 @@ common_handle_option (struct gcc_options *opts,
break;
case OPT_flto:
- opts->x_flag_lto = "";
+ opts->x_flag_lto = value ? "" : NULL;
break;
case OPT_w:
next prev parent reply other threads:[~2010-12-16 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 13:25 Andi Kleen
2010-12-16 13:26 ` [PATCH 2/2] Improve reporting of section conflict errors Andi Kleen
2010-12-16 13:32 ` Richard Guenther
2010-12-16 15:39 ` Andi Kleen
2010-12-16 15:46 ` Richard Guenther
2010-12-16 15:53 ` Andi Kleen
2010-12-16 16:56 ` Joseph S. Myers
2010-12-16 17:24 ` Andi Kleen
2010-12-16 20:37 ` H.J. Lu
2010-12-16 14:01 ` Nathan Froyd
2010-12-16 13:29 ` [PATCH 1/2] Fix -fno-lto (PR lto/46905) Richard Guenther
2010-12-16 13:30 ` Andi Kleen
2010-12-16 13:45 ` Richard Guenther
2010-12-16 16:09 ` Jan Hubicka
2010-12-16 16:44 ` Joseph S. Myers
2010-12-16 18:14 ` Andi Kleen [this message]
2010-12-18 20:44 ` Richard Guenther
2010-12-20 5:05 ` Andi Kleen
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=20101216165611.GE26663@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.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).