public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobias dot burnus at physik dot fu-berlin dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28662]  New: fpp call of gfortran: -traditional-cpp versus newer macros like #x
Date: Wed, 09 Aug 2006 14:04:00 -0000	[thread overview]
Message-ID: <bug-28662-1719@http.gcc.gnu.org/bugzilla/> (raw)

See http://gcc.gnu.org/ml/fortran/2006-08/msg00145.html

Currently gfortran calls cpp with the option -traditional-cpp. Using this
option, newer macros like
   #define msg(x) print *, #x
don't work (the #x causes the argument to be quoted). (See url/email for
example.)

I couldn't find any standard for fpp. I assume that it is only a Fortran-aware
CPP, which is defined in the C99 standard (ISO/IEC 9899:1999, section "6.10.3.2
The # operator").

I would expect that the newer constructs work by default with gfortran, or at
least that one can force that mode. The first would simply mean to remove
"-traditional-cpp" from the argument list.

Other compilers: Sun Studio f95 and Intel Fortran Compiler both support #x by
default.

g95 and NAGware f95 seem to work as gfortran: msg(test) is converted into
  print *,#hello


-- 
           Summary: fpp call of gfortran: -traditional-cpp versus newer
                    macros like #x
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tobias dot burnus at physik dot fu-berlin dot de


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


             reply	other threads:[~2006-08-09 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 14:04 tobias dot burnus at physik dot fu-berlin dot de [this message]
2006-08-09 18:03 ` [Bug fortran/28662] " pinskia at gcc dot gnu dot org
2006-08-09 18:10 ` tobias dot burnus at physik dot fu-berlin dot de
2006-10-31 13:03 ` burnus at gcc dot gnu dot org
2008-02-08 17:55 ` burnus at gcc dot gnu dot org
2008-04-23 19:30 ` burnus at gcc dot gnu dot org
2008-07-30 18:08 ` burnus at gcc dot gnu dot org
2008-08-06  6:25 ` burnus at gcc dot gnu dot org
2008-08-06  6:27 ` 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-28662-1719@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).