public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	segher@chello.nl
Subject: Re: c/4416: documentation says -fstd= but should say -std=
Date: Fri, 28 Sep 2001 02:22:00 -0000	[thread overview]
Message-ID: <20010928092201.4267.qmail@sourceware.cygnus.com> (raw)

Synopsis: documentation says -fstd= but should say -std=

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Fri Sep 28 02:22:01 2001
State-Changed-Why:
    Not a bug.  We document the external interface to the programs
    cpp, gcc and g++.  The interfaces to cpp0, cc1, cc1plus etc.
    are undocumented and subject to change.
    If -fstd= doesn't work with gcc, that is a bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4416&database=gcc


             reply	other threads:[~2001-09-28  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28  2:22 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-28  2:56 Segher Boessenkool
2001-09-28  2:36 Joseph S. Myers
2001-09-28  1:36 segher

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=20010928092201.4267.qmail@sourceware.cygnus.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=segher@chello.nl \
    /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).