public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/19180] How to Add New GCC option
Date: Thu, 15 Nov 2007 17:40:00 -0000	[thread overview]
Message-ID: <20071115174047.15119.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19180-690@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from manu at gcc dot gnu dot org  2007-11-15 17:40 -------
>From bug 26168:

"gcc/gcc.c has a comment at the top that's a guide to adding a command line
option.  It's incomplete: it should say to add the new option to c.opt and
rebuild the compiler, and then describe how the variable OPT_whatever gets
created by the awk scripts during the build process, so you can then check for
the option elsewhere in the compiler.  That mechanism doesn't appear documented
at all, and took me a while to figure out through code tracing.  Some
description in the comment would have been a big help.

Also, the comment at the top of the automatically-generated options.c file says
it's generated by "opts.sh" rather than by those awk scripts.  That's a minor
thing but updating it wouldn't hurt."


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu dot org


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


  parent reply	other threads:[~2007-11-15 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19180-690@http.gcc.gnu.org/bugzilla/>
2007-05-25 20:33 ` steven at gcc dot gnu dot org
2007-11-15 17:40 ` manu at gcc dot gnu dot org [this message]
2007-11-15 17:41 ` manu at gcc dot gnu dot org
2004-12-28 18:41 [Bug driver/19180] New: " dpatel at apple dot com
2004-12-28 18:44 ` [Bug other/19180] " pinskia at gcc dot gnu dot org
2004-12-28 18:53 ` steven at gcc dot gnu dot org
2005-03-13 17:45 ` steven at gcc dot gnu dot org
2005-04-04 21:38 ` wilson at gcc dot gnu dot 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=20071115174047.15119.qmail@sourceware.org \
    --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).