From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: fortran@gcc.gnu.org, Janne Blomqvist <blomqvist.janne@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH,Fortran] Handle 'q' exponent-letter in real-literal-constant
Date: Wed, 27 Apr 2011 22:40:00 -0000 [thread overview]
Message-ID: <20110427211014.GA34657@troutmask.apl.washington.edu> (raw)
In-Reply-To: <201104272254.40882.mikael.morin@sfr.fr>
On Wed, Apr 27, 2011 at 10:54:37PM +0200, Mikael Morin wrote:
> On Wednesday 27 April 2011 01:06:26 Steve Kargl wrote:
> >
> > It's an 'if -- else if' construct. If gfc_notify_std == FAILURE, then
> > the error message is issues and the function returns. If it is TRUE,
> > then there should be no messages and else if() is tested.
> My concern is that gfc_notify_std seems to return SUCCESS on warnings (I can't
> test right now as make has decided to rebuild the whole middle-end :-(). Then,
> I expect double warnings with -pedantic -Wreal-q-constant as -pedantic is a
> (the only one ?) case outputing warnings for GNU extensions.
>
> Mikael
laptop:kargl[220] gfc4x -pedantic -Wreal-q-constant -o z ui.f90
ui.f90:3.12:
q = 1.23q45
1
Warning: Extension: exponent-letter 'q' in real-literal-constant at (1)
laptop:kargl[221] gfc4x -pedantic -o z ui.f90
ui.f90:3.12:
q = 1.23q45
1
Warning: Extension: exponent-letter 'q' in real-literal-constant at (1)
laptop:kargl[222] gfc4x -Wreal-q-constant -o z ui.f90
ui.f90:3.12:
q = 1.23q45
1
Warning: Extension: exponent-letter 'q' in real-literal-constant at (1)
PS: People should not use -pedantic, anyway. It doesn't do what
people think it does.
--
Steve
next prev parent reply other threads:[~2011-04-27 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 19:26 Steve Kargl
2011-04-25 19:45 ` Steve Kargl
2011-04-25 19:57 ` Janne Blomqvist
2011-04-25 20:15 ` Steve Kargl
2011-04-25 21:38 ` Janne Blomqvist
2011-04-26 18:07 ` Steve Kargl
2011-04-26 18:11 ` Janne Blomqvist
2011-04-26 22:33 ` Mikael Morin
2011-04-26 23:44 ` Steve Kargl
2011-04-27 21:58 ` Mikael Morin
2011-04-27 22:40 ` Steve Kargl [this message]
2011-04-28 0:34 ` Mikael Morin
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=20110427211014.GA34657@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
/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).