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: Fri, 29 Sep 2017 09:15:00 -0000 [thread overview]
Message-ID: <CAKwh3qgZNdzPe3RAQ=weLqysAWtUSHZjYMZELQKL_nJ59Q2rdQ@mail.gmail.com> (raw)
In-Reply-To: <20170927193624.GA91517@troutmask.apl.washington.edu>
Hi Steve,
> As aside effect, the patch removes a questionable GNU Fortran
> extension that allowed arguments to IAND, IOR, and IEOR to have
> different kind type parameters. The behavior of this extension
> was not documented.
I don't really like that part. We were using the nice and convenient
mechanism of gfc_notify_std here, which allows the developer to choose
via the -std flag whether to strictly adhere to a chosen Fortran
standard or to allow GNU extensions etc. You're taking away that
flexibility and replacing it by an unconditional error. I don't
actually think that's a good idea.
In general one can argue about whether or not it's a good idea to use
non-std extensions. But I think gfortran should rather leave the
choice to its users, whether they want to use 'dirty and covenient'
code or have very strict checking. We have nice mechanisms for this,
and I do think we should keep them.
Cheers,
Janus
> 2017-09-27 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/81509
> * check.c: Rename function gfc_check_iand to gfc_check_iand_ieor_ior.
> * check.c (boz_args_check): New function. Check I and J not both BOZ.
> (gfc_check_dshift,gfc_check_iand_ieor_ior, gfc_check_ishft,
> gfc_check_and, gfc_check_merge_bits): Use it.
> * check.c (gfc_check_iand_ieor_ior): Force conversion of BOZ to kind
> type of other agrument. Remove silly GNU extension.
> (gfc_check_ieor, gfc_check_ior): Delete now unused functions.
> * intrinsic.c (add_functions): Use gfc_check_iand_ieor_ior. Wrap long
> line.
> * intrinsic.h: Rename gfc_check_iand to gfc_check_iand_ieor_ior.
> Delete prototype for bool gfc_check_ieor and gfc_check_ior
> * intrinsic.texi: Update documentation for boz-literal-constant.
>
> 2017-09-27 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/81509
> * gfortran.dg/graphite/id-26.f03: Fix non-conforming use of IAND.
> * gfortran.dg/pr81509_1.f90: New test.
> * gfortran.dg/pr81509_2.f90: New test.
>
> --
> Steve
> 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
> 20161221 https://www.youtube.com/watch?v=IbCHE-hONow
next prev parent reply other threads:[~2017-09-29 9:15 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 [this message]
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
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='CAKwh3qgZNdzPe3RAQ=weLqysAWtUSHZjYMZELQKL_nJ59Q2rdQ@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).