public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tom dot browder at fwb dot srs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18428] No preprocessing option -cpp for gfortran
Date: Tue, 07 Mar 2006 20:37:00 -0000 [thread overview]
Message-ID: <20060307203732.4773.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18428-7536@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from tom dot browder at fwb dot srs dot com 2006-03-07 20:37 -------
(In reply to comment #6)
> While I completely agree with you, I don't see a way to do that with the
> current framework. On the other hand, when (or if) we switch to cpplib, it
How does the current framework now handle the difference between source files
t.f (not preprocessed) and t.F (preprocessed). Couldn't command line arg
'-cpp' set a flag to change the handling of any source file to the same as t.F?
(I know it's probably not that easy in reality.)
--
tom dot browder at fwb dot srs dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tom dot browder at fwb dot
| |srs dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18428
next prev parent reply other threads:[~2006-03-07 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18428-7536@http.gcc.gnu.org/bugzilla/>
2005-11-24 22:11 ` fxcoudert at gcc dot gnu dot org
2006-02-26 19:11 ` pinskia at gcc dot gnu dot org
2006-03-07 20:37 ` tom dot browder at fwb dot srs dot com [this message]
2008-02-10 14:36 ` dfranke at gcc dot gnu dot org
2008-05-25 22:39 ` dfranke at gcc dot gnu dot org
2008-05-29 19:13 ` dfranke at gcc dot gnu dot org
2004-11-11 13:29 [Bug fortran/18428] New: " c dot lemmen at fz-juelich dot de
2004-11-11 15:06 ` [Bug fortran/18428] " pinskia at gcc dot gnu dot org
2005-06-12 11:37 ` c dot lemmen at fz-juelich dot de
2005-08-12 12:29 ` c dot lemmen at fz-juelich dot de
2005-08-12 12:32 ` pinskia at gcc dot gnu dot org
2005-08-12 13:23 ` c dot lemmen at fz-juelich dot de
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=20060307203732.4773.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).