public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18111] spurious warnings with -W -Wunused
Date: Fri, 05 Nov 2004 11:20:00 -0000 [thread overview]
Message-ID: <20041105112058.23577.qmail@sourceware.org> (raw)
In-Reply-To: <20041022140406.18111.martin@mpa-garching.mpg.de>
------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-11-05 11:20 -------
Subject: Re: spurious warnings with -W -Wunused
martin at mpa-garching dot mpg dot de wrote:
> ------- Additional Comments From martin at mpa-garching dot mpg dot de 2004-11-05 08:31 -------
> Since the patch has been approved
> (http://gcc.gnu.org/ml/gcc-patches/2004-10/msg02547.html),
> could someone please commit it?
> Or is it better to wait for the complete fix?
>
>
I hope to get there today, I've had very little time for gfortran work recently.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18111
next prev parent reply other threads:[~2004-11-05 11:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 14:04 [Bug fortran/18111] New: [gfortran] spurious warnings with -W -Wall martin at mpa-garching dot mpg dot de
2004-10-22 14:05 ` [Bug fortran/18111] [gfortran] spurious warnings with -W -Wunused martin at mpa-garching dot mpg dot de
2004-10-22 14:09 ` [Bug fortran/18111] " pinskia at gcc dot gnu dot org
2004-10-23 19:41 ` tobi at gcc dot gnu dot org
2004-10-26 11:15 ` martin at mpa-garching dot mpg dot de
2004-10-26 11:23 ` martin at mpa-garching dot mpg dot de
2004-10-26 17:32 ` tobi at gcc dot gnu dot org
2004-11-05 8:31 ` martin at mpa-garching dot mpg dot de
2004-11-05 11:20 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [this message]
2004-11-05 19:52 ` cvs-commit at gcc dot gnu dot org
2004-11-05 20:03 ` tobi at gcc dot gnu dot org
2005-01-09 4:46 ` giovannibajo at libero dot it
[not found] <bug-18111-2736@http.gcc.gnu.org/bugzilla/>
2005-11-20 12:10 ` martin at mpa-garching dot mpg dot de
2006-06-06 10:11 ` martin at mpa-garching dot mpg dot de
2006-06-06 10:14 ` martin at mpa-garching dot mpg dot de
2006-08-16 12:50 ` pault at gcc dot gnu dot org
2006-08-16 12:54 ` pault at gcc dot gnu dot org
2006-08-16 13:04 ` jakub at gcc dot gnu dot org
2006-08-16 21:58 ` paulthomas2 at wanadoo dot fr
2006-08-18 5:15 ` patchapp at dberlin dot org
2006-08-20 5:47 ` pault at gcc dot gnu dot org
2006-08-20 8:21 ` pault at gcc dot gnu dot org
2006-08-20 18:10 ` pault at gcc dot gnu dot org
2006-08-21 11:58 ` martin at mpa-garching dot mpg dot de
2006-08-21 13:32 ` paulthomas2 at wanadoo dot fr
2006-08-21 16:59 ` martin at mpa-garching dot mpg dot de
2006-08-21 20:13 ` paulthomas2 at wanadoo dot fr
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=20041105112058.23577.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).