public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brooks at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28122] Undocumented gfortran options
Date: Wed, 15 Nov 2006 06:06:00 -0000	[thread overview]
Message-ID: <20061115060559.20863.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28122-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from brooks at gcc dot gnu dot org  2006-11-15 06:05 -------
It turns out that we can't set -fpreprocessed to "Undocumented", as it is
shared with other front ends.  However, it is documented in the GCC manual in
the preprocessor section, and thus falls outside the "options specific to GNU
Fortran" purview of the command-line options section in the gfortran manual. 
As such, I see no need to add duplicate documentation to it in the gfortran
manual; there are already plenty of other preprocessor options that the
"gfortran" command supports that are not in the manual, and from a user
perspective this one is no different.

Meanwhile, I have also removed -no-backend and -fmodule-private, instead of
documenting them.  Thus, I'm resolving this as fixed.


-- 

brooks at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


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


      parent reply	other threads:[~2006-11-15  6:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 11:57 [Bug fortran/28122] New: " fxcoudert at gcc dot gnu dot org
2006-07-11  7:57 ` [Bug fortran/28122] " fxcoudert at gcc dot gnu dot org
2006-11-09  9:41 ` brooks at gcc dot gnu dot org
2006-11-09  9:48 ` brooks at gcc dot gnu dot org
2006-11-15  6:06 ` brooks at gcc dot gnu dot org [this message]

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=20061115060559.20863.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).