public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28662] fpp call of gfortran: -traditional-cpp versus newer macros like #x
Date: Sat, 03 Mar 2012 14:37:00 -0000	[thread overview]
Message-ID: <bug-28662-4-drbf9jRkJ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28662-4@http.gcc.gnu.org/bugzilla/>

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

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |franke.daniel at gmail dot
                   |                            |com

--- Comment #9 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2012-03-03 14:36:27 UTC ---
*** Bug 29671 has been marked as a duplicate of this bug. ***


       reply	other threads:[~2012-03-03 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28662-4@http.gcc.gnu.org/bugzilla/>
2012-03-03 14:37 ` fxcoudert at gcc dot gnu.org [this message]
2014-12-11 16:21 ` burnus at gcc dot gnu.org
2015-08-30 14:37 ` dominiq at lps dot ens.fr
2021-08-27  2:15 ` pinskia at gcc dot gnu.org
2006-08-09 14:04 [Bug fortran/28662] New: " tobias dot burnus at physik dot fu-berlin dot de
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-4-drbf9jRkJ3@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).