public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58100] Spurious "DO loop at (1) will be executed zero times" warning
Date: Sun, 18 Aug 2013 20:24:00 -0000 [thread overview]
Message-ID: <bug-58100-4-cQJOv4EGaH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58100-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58100
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> Still present after r201658 (pr56666, after it -Wall is needed).
With that patch, -W(no-)zerotrip permits to toggle the warning, which I think
it sufficient. Everything else requires more analysis (e.g. the "if"'s else
branch is never executed in this case), which I believe is not worthwhile.
Roland: Is the new warning option -W(no-)zerotrip sufficient for you?
(Side remark: there are conflicts with early optimization: For debugging, no
folding/simplification should be done by front-ends. On the other hand, some
simplification is useful - and the ME is too late for it.]
next prev parent reply other threads:[~2013-08-18 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 9:31 [Bug fortran/58100] New: " roland.kaufmann at uni dot no
2013-08-13 14:47 ` [Bug fortran/58100] " dominiq at lps dot ens.fr
2013-08-17 22:22 ` tkoenig at gcc dot gnu.org
2013-08-18 20:24 ` burnus at gcc dot gnu.org [this message]
2013-08-22 8:23 ` roland.kaufmann at uni dot no
2013-08-28 13:57 ` tkoenig at gcc dot gnu.org
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=bug-58100-4-cQJOv4EGaH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).