public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33502] gfortran with .F suffix and -g3 option chokes on preprocessor syntax
Date: Thu, 20 Sep 2007 09:19:00 -0000 [thread overview]
Message-ID: <20070920091909.31674.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33502-13351@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pinskia at gcc dot gnu dot org 2007-09-20 09:19 -------
Subject: Re: gfortran with .F suffix and -g3 option chokes on preprocessor
syntax
On 20 Sep 2007 08:08:00 -0000, fxcoudert at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-09-20 08:07 -------
> Confirmed. Andrew, what is the front-end expected to do with the #defines? I
> suspect that we need to pass them to the middle-end, by calling
> debug_hooks->define and debug_hooks->undef (as is done in c-lex.c).
Yes that should be enough.
Thanks,
Andrew Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33502
next prev parent reply other threads:[~2007-09-20 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 18:51 [Bug fortran/33502] New: " sjc at pobox dot com
2007-09-19 18:58 ` [Bug fortran/33502] " pinskia at gcc dot gnu dot org
2007-09-20 8:08 ` fxcoudert at gcc dot gnu dot org
2007-09-20 9:19 ` pinskia at gcc dot gnu dot org [this message]
2007-09-20 9:34 ` fxcoudert at gcc dot gnu dot org
2007-09-22 15:03 ` fxcoudert at gcc dot gnu dot org
2007-09-22 15:04 ` fxcoudert at gcc dot gnu dot org
2007-09-24 20:28 ` fxcoudert at gcc dot gnu dot org
2007-10-01 0:05 ` fxcoudert at gcc dot gnu dot org
2007-10-04 15:04 ` fxcoudert at gcc dot gnu dot org
2007-10-04 15:06 ` fxcoudert 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=20070920091909.31674.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).