public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36342] [4.4 Regression] Missing file name in compilation diagnostics of preprocessed fortran source
Date: Wed, 18 Jun 2008 07:18:00 -0000	[thread overview]
Message-ID: <20080618071734.25058.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36342-10601@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from pault at gcc dot gnu dot org  2008-06-18 07:17 -------
(In reply to comment #10)
> Reopened. 

Hah! OK - thanks

Paul *with tail between his legs*


-- 


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


  parent reply	other threads:[~2008-06-18  7:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 11:58 [Bug fortran/36342] New: Missing file name in compilation diagnostics with '-cpp' or '-x f95-cpp-input' P dot Schaffnit at access dot rwth-aachen dot de
2008-05-27 15:22 ` [Bug fortran/36342] " dfranke at gcc dot gnu dot org
2008-05-28 11:06 ` P dot Schaffnit at access dot rwth-aachen dot de
2008-06-02 18:56 ` [Bug middle-end/36342] [4.4 Regression] Missing file name in compilation diagnostics of preprocessed fortran source dfranke at gcc dot gnu dot org
2008-06-06  8:27 ` dfranke at gcc dot gnu dot org
2008-06-06  8:30 ` P dot Schaffnit at access dot rwth-aachen dot de
2008-06-06 10:42 ` [Bug fortran/36342] " dfranke at gcc dot gnu dot org
2008-06-11 11:13 ` jsm28 at gcc dot gnu dot org
2008-06-13 21:19 ` burnus at gcc dot gnu dot org
2008-06-16 17:57 ` burnus at gcc dot gnu dot org
2008-06-16 20:23 ` pault at gcc dot gnu dot org
2008-06-16 21:50 ` dfranke at gcc dot gnu dot org
2008-06-18  7:18 ` pault at gcc dot gnu dot org [this message]
2008-06-18  7:21 ` P dot Schaffnit at access dot rwth-aachen dot de
2008-06-18 15:44 ` burnus at gcc dot gnu dot org
2008-06-18 16:49 ` dfranke at gcc dot gnu dot org
2008-06-20 14:01 ` laurynas dot biveinis at gmail dot com
2008-07-17 13:31 ` burnus at gcc dot gnu dot org
2008-07-18 16:51 ` rguenth at gcc dot gnu dot org
2008-07-19 18:28 ` burnus at gcc dot gnu dot org
2008-07-19 18:31 ` 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=20080618071734.25058.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).