public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fkrogh#gcc at mathalacarte dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61002] New: Can't divide by 0
Date: Tue, 29 Apr 2014 13:52:00 -0000	[thread overview]
Message-ID: <bug-61002-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61002

            Bug ID: 61002
           Summary: Can't divide by 0
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fkrogh#gcc at mathalacarte dot com

If I have a statement like

real(kind(1.0d0)), parameter :: big=1.0d0/0.0d0

the compile fails with an error even when using the option -ffpe-trap=

The man page for gcc makes this excellent point

       -Wno-div-by-zero
           Do not warn about compile-time integer division by zero.  Floating-
           point division by zero is not warned about, as it can be a
           legitimate way of obtaining infinities and NaNs.

And in fact, all I'm trying to do is obtain infinity.


             reply	other threads:[~2014-04-29 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 13:52 fkrogh#gcc at mathalacarte dot com [this message]
2014-04-29 14:06 ` [Bug fortran/61002] " dominiq at lps dot ens.fr
2014-04-29 14:53 ` fkrogh#gcc at mathalacarte dot com
2014-05-01 22:17 ` dominiq at lps dot ens.fr
2014-05-01 22:22 ` fkrogh#gcc at mathalacarte dot com
2014-05-01 22:27 ` dominiq at lps dot ens.fr
2014-05-02 12:08 ` burnus at gcc dot gnu.org
2014-05-02 14:24 ` dominiq at lps dot ens.fr
2014-05-03  7:21 ` schwab@linux-m68k.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-61002-4@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).