public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31547]  New: Document when CPP is called and document the f95-cpp-input option
Date: Thu, 12 Apr 2007 14:04:00 -0000	[thread overview]
Message-ID: <bug-31547-13404@http.gcc.gnu.org/bugzilla/> (raw)

Currently, nowhere is documented that gfortran calls for .F, .FPP, .F90, .F95
and  .F2003 the C Preprocessor (in the traditional mode, cf. PR 18428).

I don't know whether it fits better to gfortran.texi or invoke.texi.

In addition, we don't document the option to call the preprocessor for files
without capital letter (this is especially needed on operating systems where
the file extension is case insensitive):
 -x f95-cpp-input
 -x f77-cpp-input

and how to suppress the calling of the preprocessor, i.e.
 -x f77
 -x f95

"f95" and "f95-cpp-input" are documented (or rather mentioned) in gcc(1).
However, one should also add f77 and f77-cpp-input to the gcc manpage.

(Cross ref: a "-cpp" option is proposed for gfortran in PR 18428)


-- 
           Summary: Document when CPP is called and document the f95-cpp-
                    input option
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


             reply	other threads:[~2007-04-12 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 14:04 burnus at gcc dot gnu dot org [this message]
2007-04-18  6:01 ` [Bug fortran/31547] " fxcoudert at gcc dot gnu dot org
2007-09-06 18:53 ` burnus at gcc dot gnu dot org
2007-09-08 14:00 ` patchapp at dberlin dot org
2007-09-10 12:09 ` burnus at gcc dot gnu dot org
2007-09-10 12:09 ` burnus 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=bug-31547-13404@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).