public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/48524] spec language does not cover switches with separated form
Date: Sat, 09 Apr 2011 11:28:00 -0000	[thread overview]
Message-ID: <bug-48524-4-ZN0Gan0RaK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48524-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48524

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-04-09 11:28:33 UTC ---
Specs are an internal GCC implementation detail, subject to change 
whenever convenient for implementation purposes.  (Whoever put 
documentation for them in invoke.texi was wrong to do so - and as far as I 
know, did not have FSF permission either for copying text from gcc.c under 
one license to invoke.texi under another - the comment starting "Specs are 
strings containing lines" is the proper documentation for specs.)  My 
recommendation in 
<http://gcc.gnu.org/ml/gcc-patches/2011-02/msg01486.html> for certain 
broken -D specs in GCC was that any required semantics should be moved 
into cc1.  We have for a long time been moving away from defining built-in 
macros in specs, towards defining them based on actual logical state 
derived from option processing.  In any case if you wish to submit a patch 
for some new specs feature I would suggest you include the 
--enable-fortify-source=2 or similar configure option with it to provide 
some actual use for that feature in GCC.  Note that the spec you give 
appears wrong in that any -D_FORTIFY_SOURCE or -D_FORTIFY_SOURCE=<value> 
option passed by the user should presumably also disable a default 
-D_FORTIFY_SOURCE=2 option; maybe you actually want an 
if-macro-not-defined spec function that covers all these cases.


  reply	other threads:[~2011-04-09 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09  2:35 [Bug driver/48524] New: " dirtyepic at gentoo dot org
2011-04-09 11:28 ` joseph at codesourcery dot com [this message]
2011-04-09 18:51 ` [Bug driver/48524] " dirtyepic at gentoo dot org
2011-04-10  0:27 ` joseph at codesourcery dot com
2011-04-12  2:22 ` vapier at gentoo dot org
2011-04-13  3:49 ` dirtyepic at gentoo dot org
2011-12-17 20:33 ` zorry at gentoo dot org
2011-12-17 21:22 ` zorry at gentoo dot org
2011-12-18 20:46 ` zorry at gentoo dot org
2012-02-08 21:38 ` jsm28 at gcc dot gnu.org

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=bug-48524-4-ZN0Gan0RaK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).