From: Janus Weil <janus@gcc.gnu.org>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix fortran/81509
Date: Tue, 03 Oct 2017 19:38:00 -0000 [thread overview]
Message-ID: <CAKwh3qgQR83b7FsAM+t16G=3mfAWgiTXWmW0L88G0OuQ6SnCog@mail.gmail.com> (raw)
In-Reply-To: <20171003181010.GA23841@troutmask.apl.washington.edu>
2017-10-03 20:10 GMT+02:00 Steve Kargl <sgk@troutmask.apl.washington.edu>:
>> > There is no mechanism available to warn the user of nonstandard code.
>>
>> Of course there is:
>>
>> $ gfortran -std=f2008 a.f90
>> a.f90:4:17:
>>
>> print *, iand(i,j)
>> 1
>> Error: GNU Extension: Different type kinds at (1)
>>
>
> Reread what I wrote. There is NO MECHANISM TO WARN the user.
> -std=f2008 does not produce a WARNING. It produces an ERROR.
Sorry, I'm currently traveling and must have misread that.
Anyway, I don't have the feeling this discussion is going anywhere. I
said my opinion, you heard it. You have two OKs, so just go ahead and
commit the patch. I really don't care.
Cheers,
Janus
next prev parent reply other threads:[~2017-10-03 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 19:36 Steve Kargl
2017-09-28 9:46 ` Paul Richard Thomas
2017-09-28 17:41 ` Steve Kargl
2017-09-29 9:15 ` Janus Weil
2017-09-29 14:08 ` Steve Kargl
2017-10-01 17:42 ` Janus Weil
2017-10-01 18:04 ` Janne Blomqvist
2017-10-01 19:58 ` Steve Kargl
2017-10-03 14:27 ` Janus Weil
2017-10-03 18:10 ` Steve Kargl
2017-10-03 19:38 ` Janus Weil [this message]
2017-10-04 6:02 ` Steve Kargl
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='CAKwh3qgQR83b7FsAM+t16G=3mfAWgiTXWmW0L88G0OuQ6SnCog@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).