public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/57628] spurious error: division by zero in if statement Date: Sun, 16 Jun 2013 14:55:00 -0000 [thread overview] Message-ID: <bug-57628-4-nJfSVUb77Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57628-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57628 --- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Sun, Jun 16, 2013 at 07:57:23AM +0000, furue at hawaii dot edu wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57628 > > --- Comment #2 from Ryo Furue <furue at hawaii dot edu> --- > > Of course. I agree with all your statements. > > And your entirely entirely miss the point! > No, I did not miss your point. > This is a "quality of implementation" issue. So, the compiler should just arbitrarily chose to evaluate some expression and ignore others? > The question is "Is refusing to compile it the best way to deal with this > error?" My answer is no. Since, > > real, parameter:: a = 0 > If (a > 0) then So, the compiler should evaluate "a > 0", but it should > write(*,*) 1/a !! this part not evaluate "1/a". > end if > > the contents of the IF statement is unreachable, the compiler more > appropriately would issue an "unreachable statements" warning > and disregard the contents of the unreachable code. DCE will take care of unreachable code in the middle-end. Just remove the PARAMETER attribute in your code, it it will do what you. real :: a = 0 if (a > 0) then print *, 1/a else print *, 'doh!' end if end
next prev parent reply other threads:[~2013-06-16 14:55 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-16 6:39 [Bug fortran/57628] New: " furue at hawaii dot edu 2013-06-16 7:22 ` [Bug fortran/57628] " kargl at gcc dot gnu.org 2013-06-16 7:57 ` furue at hawaii dot edu 2013-06-16 8:13 ` furue at hawaii dot edu 2013-06-16 8:26 ` pinskia at gcc dot gnu.org 2013-06-16 8:47 ` furue at hawaii dot edu 2013-06-16 8:50 ` furue at hawaii dot edu 2013-06-16 14:34 ` dominiq at lps dot ens.fr 2013-06-16 14:55 ` sgk at troutmask dot apl.washington.edu [this message] 2013-06-16 23:28 ` furue at hawaii dot edu 2013-06-16 23:33 ` furue at hawaii dot edu 2013-06-17 5:00 ` sgk at troutmask dot apl.washington.edu 2013-06-17 5:00 ` sgk at troutmask dot apl.washington.edu 2013-06-17 18:54 ` anlauf at gmx dot de 2013-06-17 21:25 ` furue at hawaii dot edu 2013-06-17 21:42 ` furue at hawaii dot edu 2013-06-18 1:47 ` furue at hawaii dot edu 2013-06-18 1:56 ` furue at hawaii dot edu
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-57628-4-nJfSVUb77Z@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: linkBe 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).