public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "domob at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39171] Misleading warning for negative character length
Date: Tue, 09 Feb 2010 10:44:00 -0000 [thread overview]
Message-ID: <20100209104446.23415.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39171-16338@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from domob at gcc dot gnu dot org 2010-02-09 10:44 -------
Subject: Bug 39171
Author: domob
Date: Tue Feb 9 10:44:33 2010
New Revision: 156620
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156620
Log:
2010-02-09 Daniel Kraft <d@domob.eu>
PR fortran/39171
* resolve.c (resolve_charlen): Change warning about negative CHARACTER
length to be correct and issue only with -Wsurprising.
* invoke.texi (Wsurprising): Mention this new warning that is
turned on by -Wsurprising.
2010-02-09 Daniel Kraft <d@domob.eu>
PR fortran/39171
* gfortran.dg/char_length_2.f90: Change warning expectations
accordingly
and pass -Wsurprising as necessary.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/char_length_2.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39171
next prev parent reply other threads:[~2010-02-09 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:19 [Bug fortran/39171] New: " domob at gcc dot gnu dot org
2009-02-13 10:34 ` [Bug fortran/39171] " burnus at gcc dot gnu dot org
2009-02-19 5:56 ` pault at gcc dot gnu dot org
2009-12-27 9:35 ` domob at gcc dot gnu dot org
2010-02-09 10:44 ` domob at gcc dot gnu dot org [this message]
2010-02-09 10:45 ` domob at gcc dot gnu dot org
2010-02-23 16:39 ` hjl dot tools at gmail dot com
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=20100209104446.23415.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).