public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18452] Fortran options induces warning for fortran that needs preprocessing
Date: Fri, 04 Nov 2005 08:31:00 -0000	[thread overview]
Message-ID: <20051104083121.14152.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18452-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from fxcoudert at gcc dot gnu dot org  2005-11-04 08:31 -------
Hurray, hurray, this bug is fixed! Now, could we get libgfortran building with
-Werror? :)


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
   GCC host triplet|i686-gnu-linux              |
         Resolution|                            |FIXED
   Target Milestone|---                         |4.0.3


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


  parent reply	other threads:[~2005-11-04  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18452-10259@http.gcc.gnu.org/bugzilla/>
2005-10-13  7:50 ` c dot lemmen at fz-juelich dot de
2005-11-02 21:57 ` fxcoudert at gcc dot gnu dot org
2005-11-04  8:29 ` fxcoudert at gcc dot gnu dot org
2005-11-04  8:31 ` fxcoudert at gcc dot gnu dot org [this message]
2004-11-12 15:15 [Bug fortran/18452] New: -fno-second-underscore induces warning coudert at clipper dot ens dot fr
2005-08-01 13:16 ` [Bug fortran/18452] Fortran options induces warning for fortran that needs preprocessing pinskia at gcc dot gnu dot org
2005-08-23 15:07 ` pinskia 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=20051104083121.14152.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).