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/37032] including "file.F90" - no CPP processing
Date: Tue, 05 Aug 2008 19:23:00 -0000 [thread overview]
Message-ID: <20080805192214.26644.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37032-16565@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from burnus at gcc dot gnu dot org 2008-08-05 19:22 -------
Cf. multiple topic PR 35707.
The problem is that
include 'file2.F95'
is not processed through CPP. I'm not sure whether it should and when it should
(file extension .F/F90/F95/F03/F08/FPP/FOR/fpp, always, or never).
One possibility is to use:
#include "file2.F95"
in this case CPP includes the file before it hands it to the Fortran part of
the compiler.
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Multi-line comments in an |including "file.F90" - no
|included file trigger |CPP processing
|invalid character |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37032
next prev parent reply other threads:[~2008-08-05 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 18:52 [Bug fortran/37032] New: Multi-line comments in an included file trigger invalid character godom at twinbee dot com
2008-08-05 19:23 ` burnus at gcc dot gnu dot org [this message]
2008-08-05 21:09 ` [Bug fortran/37032] including "file.F90" - no CPP processing godom at twinbee dot com
2008-08-05 21:19 ` kargl at gcc dot gnu dot org
2008-08-05 21:31 ` godom at twinbee dot com
2008-08-05 21:45 ` kargl at gcc dot gnu dot org
2008-08-05 22:06 ` godom at twinbee dot com
2008-08-06 6:14 ` burnus at gcc dot gnu dot org
2008-08-14 21:18 ` dfranke at gcc dot gnu dot org
2008-08-18 20:48 ` dfranke at gcc dot gnu dot org
2008-08-18 20:52 ` dfranke 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=20080805192214.26644.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).