public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "shobbo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55210] New: cannot #define FOO 'a'
Date: Mon, 05 Nov 2012 02:22:00 -0000	[thread overview]
Message-ID: <bug-55210-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55210
           Summary: cannot #define FOO 'a'
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: shobbo@gmail.com


If I define a macro as in the summary I get the following output:

[*] gfortran  -cpp testfort.f -o testfort
<built-in>:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.

I tried it with -cpp, -xf95-cpp-input and -xf77-cpp-input.
using gfortran 4.7.2, 4.4.3 and 4.4.4.

!---- testfort.f
#define FOO 'a'

      program testfort
        implicit none
        print *, 'pretest'
#if FOO == 'a'
        print *, "the macro is a character a"
#endif
        print *, 'epitest'
      end program


             reply	other threads:[~2012-11-05  2:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05  2:22 shobbo at gmail dot com [this message]
2012-11-05 15:32 ` [Bug fortran/55210] cannot use macro #define FOO 'a' in a conditional burnus at gcc dot gnu.org
2021-08-27  1:46 ` pinskia at gcc dot gnu.org
2021-08-27  1:50 ` pinskia at gcc dot gnu.org
2021-08-27  1:54 ` pinskia at gcc dot gnu.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-55210-4@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).