From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Jan Hubicka <jh@suse.de>,
Diego Novillo <dnovillo@google.com>
Subject: Re: [PATCH][2/n] LTO option handling/merging rewrite
Date: Sun, 30 Oct 2011 19:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1110301632130.32251@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFiYyc1Y+LdcMRe4P1xKUzcp8qpqhfDLUTg9NH=LKMU47eQH6g@mail.gmail.com>
On Sat, 29 Oct 2011, Richard Guenther wrote:
> I tried to look at what we get for -fno-pic vs. -fpic and -fno-pic is completely
> dropped from the decoded options list (not sure what happens on targets
> with -fpic as default). So it seems at most one state (the non-default one)
> survives here.
I don't see where that would happening, and don't see that myself;
-fno-pic gets included in COLLECT_GCC_OPTIONS for me if it's the last
-fpic/-fno-pic option on the driver command line.
> But maybe I'm missing something - how can I reliably check if there is
> a negative form of an option, and if, if the option is the negative form?
The "value" field of a cl_decoded_option is 1 for a positive option, 0 for
the negative form, for an option accepting positive and negative forms
(not marked with RejectNegative / CL_REJECT_NEGATIVE. (It's a bug if an
option allows a negative form but also takes a UInteger argument, since
such an argument also uses the "value" field.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-10-30 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 12:52 Richard Guenther
2011-10-28 15:20 ` Diego Novillo
2011-10-30 22:30 ` Richard Guenther
2011-10-28 15:56 ` Joseph S. Myers
2011-10-30 1:13 ` Richard Guenther
2011-10-30 19:01 ` Joseph S. Myers [this message]
2011-11-02 11:43 ` Richard Guenther
2023-01-17 9:46 ` Andreas Schwab
2011-10-28 15:59 ` Jack Howarth
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=Pine.LNX.4.64.1110301632130.32251@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.de \
--cc=rguenther@suse.de \
--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).