public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "quantheory at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support
Date: Tue, 04 Dec 2012 19:28:00 -0000	[thread overview]
Message-ID: <bug-29383-4-mB5mIK5cSj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29383-4@http.gcc.gnu.org/bugzilla/>


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

Sean Santos <quantheory at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |quantheory at gmail dot com

--- Comment #10 from Sean Santos <quantheory at gmail dot com> 2012-12-04 19:28:19 UTC ---
Comment 9 seems a bit too pessimistic to me.

For one, returning ".false." for ieee_supports_* doesn't seem like a sidestep,
but more like the correct behavior in an environment that lacks IEEE support
(maybe even if the only reason is because the compiler has not implemented it).

For another, as noted above, one important use of the ieee_arithmetic module is
to test for NaN/Inf in a standard-conforming way, rather than using
compiler-specific extensions. (AFAIK, gfortran is the only F2003 compiler that
forces you to use a non-portable extension to do this.)

For that functionality, the only likely problem I can see is in deciding when
e.g. ieee_support_nan should return ".true.".

Of course this is only a fraction of what needs to be done (presumably the
easiest part), but it's much better than nothing, particularly to address what
I would expect to be one of the most common uses of this module.


  parent reply	other threads:[~2012-12-04 19:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29383-4@http.gcc.gnu.org/bugzilla/>
2011-01-24  9:41 ` thenlich at users dot sourceforge.net
2011-07-22 17:55 ` longb at cray dot com
2012-10-07  0:09 ` kargl at gcc dot gnu.org
2012-10-09 15:19 ` andy.nelson at lanl dot gov
2012-10-09 17:01 ` kargl at gcc dot gnu.org
2012-12-04 19:28 ` quantheory at gmail dot com [this message]
2013-04-14 20:09 ` quantheory at gmail dot com
2014-01-06 11:33 ` janus at gcc dot gnu.org
2014-06-03 18:15 ` w6ws at earthlink dot net
2014-06-07 10:19 ` fxcoudert at gcc dot gnu.org
2014-06-07 10:19 ` fxcoudert at gcc dot gnu.org
2014-06-07 10:23 ` fxcoudert at gcc dot gnu.org
2014-06-07 10:25 ` fxcoudert at gcc dot gnu.org
2014-06-15 16:57 ` fxcoudert at gcc dot gnu.org
2014-06-28 14:18 ` fxcoudert at gcc dot gnu.org
2014-06-28 15:11 ` fxcoudert at gcc dot gnu.org
2022-09-10 13:43 ` vital.had at gmail dot com
2006-10-08  8:41 [Bug fortran/29383] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-10-22  7:20 ` [Bug fortran/29383] " fxcoudert at gcc dot gnu dot org
2009-09-07  8:07 ` burnus at gcc dot gnu dot org
2010-04-14  6:33 ` burnus at gcc dot gnu dot org
2010-06-12 12:15 ` burnus at gcc dot gnu dot 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-29383-4-mB5mIK5cSj@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).