From: Janus Weil <janus@gcc.gnu.org>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 85599: warn about short-circuiting of logical expressions for non-pure functions
Date: Tue, 17 Jul 2018 07:52:00 -0000 [thread overview]
Message-ID: <CAKwh3qgwS1JFfOHLesVwwdJDUVGao2TeTv6TpDOgrYJWNU=0yA@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qgdo8yePkoaj9JE5ZcbkJSsDJpxZrUdO_UVz1o_A1LNEQ@mail.gmail.com>
> 2018-07-16 21:50 GMT+02:00 Thomas Koenig <tkoenig@netcologne.de>:
>> What I would suggest is to enable -Wfunction-eliminiation with
>> -Wextra and also use that for your new warning.
>
> Thanks for the comments. Makes sense. Updated patch attached.
Huh, after actually trying -Wfunction-elimination, I'm not so sure any
more if it really makes sense to throw the new warnings in there,
mainly for two reasons:
a) -Wfunction-elimination is slightly different, in that it warns
about removing *any* kind of function, not just impure ones. This
makes it pretty verbose, and I'm not sure why one would need to know
if a pure function call is removed.
b) It gives warnings on places that I don't understand. Simple example:
subroutine sub(r)
implicit none
real, intent(in) :: r
if ((abs(r) > 1e6) .or. (abs(r) < 1e-6)) then
print *, "rrr"
end if
end
Compiling this with "gfortran-8 -O1 -Wfunction-elimination" gives me:
if ((abs(r) > 1e6) .or. (abs(r) < 1e-6)) then
1
Warning: Removing call to function ‘abs’ at (1) [-Wfunction-elimination]
Why can I remove the call to ABS there? If I read the dump correctly,
then the two calls to ABS are optimized into a single one, which is
used for both comparisons via a temporary. Is that what the warning is
trying to tell me? And if yes, why should I care (if the function is
pure)? The middle-end certainly does tons of optimizations that
rearrange various expressions, without warning me about it ...
In other words: Does it make sense to tone down
-Wfunction-elimination, by only warning about impure functions? (We
certainly have the diagnostic capabilites for this.) If not, I'd
rather have a separate flag for the new warnings.
-Wfunction-elimination is just too noisy for my taste in its current
form.
Cheers,
Janus
next prev parent reply other threads:[~2018-07-17 7:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 21:06 Janus Weil
2018-07-12 19:43 ` Janus Weil
2018-07-13 8:03 ` Janus Weil
2018-07-15 20:39 ` Janus Weil
2018-07-15 20:57 ` Thomas Koenig
2018-07-16 8:07 ` Janus Weil
2018-07-16 19:51 ` Thomas Koenig
2018-07-17 5:08 ` Janus Weil
2018-07-17 7:52 ` Janus Weil [this message]
2018-07-17 14:32 ` Janus Weil
2018-07-17 15:19 ` Fritz Reese
2018-07-17 17:19 ` Janus Weil
2018-07-17 17:34 ` Thomas Koenig
2018-07-17 18:36 ` Janus Weil
2018-07-17 18:55 ` Fritz Reese
2018-07-17 19:21 ` Janus Weil
2018-07-18 18:43 ` Janus Weil
2018-07-12 11:17 Dominique d'Humières
2018-07-12 14:12 ` Janus Weil
2018-07-12 14:35 ` Dominique d'Humières
2018-07-12 14:55 ` Janus Weil
2018-07-12 19:53 ` Thomas Koenig
2018-07-12 20:03 ` 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='CAKwh3qgwS1JFfOHLesVwwdJDUVGao2TeTv6TpDOgrYJWNU=0yA@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).