From: Janus Weil <janus@gcc.gnu.org>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: Thomas Koenig <tkoenig@netcologne.de>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 57160: short-circuit IF only with -ffrontend-optimize
Date: Mon, 06 Aug 2018 20:59:00 -0000 [thread overview]
Message-ID: <CAKwh3qggW=_pnb3-kvJif9SoC9p2bdFaSDTTxfdKZrEgT7ea-Q@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qiFutRu9ZobZWXY5wGvSBdgLdT9VkHDOMtV=0QSQNSOJg@mail.gmail.com>
2018-08-01 22:46 GMT+02:00 Janus Weil <janus@gcc.gnu.org>:
> 2018-07-28 10:03 GMT+02:00 Janus Weil <janus@gcc.gnu.org>:
>> 2018-07-27 18:42 GMT+02:00 Dominique d'Humières <dominiq@lps.ens.fr>:
>>>> If there is further constructive criticism regarding v3 of the patch,
>>>> as posted at https://gcc.gnu.org/ml/fortran/2018-07/msg00103.html,
>>>> I'll be happy to deal with that. If not, I'd like to commit it by the
>>>> weekend.
>>>
>>> This patch breaks backward compatibility
>>
>> Not for valid Fortran code. The patch only affects code that is not
>> guaranteed to work by the Fortran standard, like "if (associated(a)
>> .and. a>0)".
>>
>> "Breaking" such code is precisely the purpose of the patch. The idea
>> is to discourage users from writing such code, because it is not valid
>> Fortran code (and therefore not portable). Are you trying to argue
>> that such code should work with gfortran?
>>
>>
>>> Hence I am definitively against this patch.
>>
>> If you are against it, do you have *any* other solution for the problem at hand?
>
> Ping!
>
> We have a problem here which deserves a solution. So, Dominique, if
> you don't like my solution, how do you propose to solve PR 57160?
ping**2
It's so easy to scream "bullshit", and so hard to find a good
solution. Still, we need one ...
I suggest the naysayers get active. I'm out.
Cheers,
Janus
next prev parent reply other threads:[~2018-08-06 20:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:42 Dominique d'Humières
2018-07-28 8:03 ` Janus Weil
2018-08-01 20:46 ` Janus Weil
2018-08-06 20:59 ` Janus Weil [this message]
2018-08-07 10:11 ` Dominique d'Humières
2018-08-07 17:14 ` Janus Weil
2018-08-07 22:21 ` Thomas König
2018-08-08 0:17 ` William Clodius
2018-08-08 5:41 ` Janus Weil
2018-08-08 8:35 ` Manfred Schwarb
2018-08-08 11:23 ` Janus Weil
2018-08-08 11:29 ` Arjen Markus
2018-08-08 18:21 ` Janus Weil
2018-08-08 20:48 ` Janus Weil
2018-08-09 1:05 ` Jerry DeLisle
2018-08-09 21:14 ` Janus Weil
2018-08-10 0:38 ` Jerry DeLisle
2018-08-10 14:14 ` Janus Weil
2018-08-08 19:50 ` Janus Weil
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 9:12 Dominique d'Humières
2018-07-24 13:46 ` Janus Weil
2018-07-24 15:42 ` Janne Blomqvist
2018-07-24 16:18 ` Janus Weil
2018-07-20 21:38 Janus Weil
2018-07-23 7:40 ` Adam Hirst
2018-07-23 17:11 ` Janus Weil
2018-07-23 21:06 ` Fritz Reese
2018-07-24 18:46 ` Janus Weil
2018-07-24 19:49 ` Janus Weil
2018-07-24 19:50 ` Thomas Koenig
2018-07-24 20:14 ` Janus Weil
2018-07-25 20:05 ` Janus Weil
2018-07-25 20:59 ` Nicolas Koenig
2018-07-25 21:01 ` Thomas Koenig
2018-07-25 21:31 ` Janus Weil
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='CAKwh3qggW=_pnb3-kvJif9SoC9p2bdFaSDTTxfdKZrEgT7ea-Q@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).