public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30694] minval/maxval with +/-Inf Date: Mon, 05 Feb 2007 19:41:00 -0000 [thread overview] Message-ID: <20070205194047.13623.qmail@sourceware.org> (raw) In-Reply-To: <bug-30694-10391@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from burnus at gcc dot gnu dot org 2007-02-05 19:40 ------- As Dick Hendrickson points out in c.l.fortran: 13.7 (the function descriptions) says "A program is prohibited from invoking an intrinsic procedure under circumstances where a value to be returned in a subroutine argument or function result is outside the range of values representable by objects of the specified type and type parameters, unless the intrinsic module IEEE ARITHMETIC (section 14) is accessible and there is support for an infinite or a NaN result, as appropriate." And IEEE: http://754r.ucbtest.org/drafts/754r.pdf "Operations on infinite operands are usually exact and therefore signal no exceptions." "Every general-computational and quiet-computational operation involving one or more input NaNs, none of them signaling, shall signal no exception, except fusedMultiplyAdd (see 9.2) . For an operation with quiet NaN inputs other than max and min operations, if a floating-point result is to be delivered, the result shall be a quiet NaN, which should be one of the input NaNs." "minNum(x,y) is the canonical floating-point number x if x < y, y if y < x, the canonicalized floatingpoint number if one operand is a floating-point number and the other a NaN. Otherwise it is either x or y. maxNum(x,y) is the canonical floating-point number y if x < y, x if y < x, the canonicalized floatingpoint number if one operand is a floating-point number and the other a NaN. Otherwise it is either x or y." Min/maxval should return (for REAL): +INF if there is an INF in the maxval argument array -INF if there is a -INF in the minval argument array NAN if the argument array only consists of NAN -HUGE or HUGE if there the array is zero-dimensional (after masking) (for the other cases the obvious min/max values of the arguments) For INTEGERs, we only have: -HUGE-1 / +HUGE for a zero-dimensional array (after masking) (for the other cases the obvious min/max) as NAN and +/-INF don't exists (cf. PR30512). -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-02-05 19:40:47 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30694
next prev parent reply other threads:[~2007-02-05 19:41 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-03 16:17 [Bug fortran/30694] New: " tkoenig at gcc dot gnu dot org 2007-02-03 16:41 ` [Bug fortran/30694] " burnus at gcc dot gnu dot org 2007-02-03 19:28 ` tkoenig at gcc dot gnu dot org 2007-02-03 20:28 ` pinskia at gcc dot gnu dot org 2007-02-04 0:19 ` burnus at gcc dot gnu dot org 2007-02-05 19:41 ` burnus at gcc dot gnu dot org [this message] 2007-02-06 12:12 ` [Bug libfortran/30694] " fxcoudert at gcc dot gnu dot org 2007-02-06 12:30 ` burnus at gcc dot gnu dot org 2007-02-07 17:55 ` tkoenig at gcc dot gnu dot org 2007-02-14 20:21 ` fxcoudert at gcc dot gnu dot org 2007-03-25 9:49 ` fxcoudert at gcc dot gnu dot org 2007-03-25 20:05 ` tkoenig at gcc dot gnu dot org 2007-04-10 19:58 ` tkoenig at gcc dot gnu dot org 2007-04-15 21:12 ` tkoenig at gcc dot gnu dot org 2007-04-18 21:59 ` fxcoudert at gcc dot gnu dot org 2007-04-19 20:03 ` tkoenig at gcc dot gnu dot org 2007-05-14 21:37 ` mmitchel at gcc dot gnu dot org 2007-05-17 13:40 ` tkoenig at gcc dot gnu dot org 2007-06-15 18:56 ` tkoenig at gcc dot gnu dot org 2007-06-15 18:56 ` tkoenig at gcc dot gnu dot org 2007-06-21 18:12 ` pault at gcc dot gnu dot org 2007-07-20 3:49 ` mmitchel at gcc dot gnu dot org 2007-08-08 15:08 ` fxcoudert at gcc dot gnu dot org 2007-10-09 19:28 ` mmitchel at gcc dot gnu dot org 2007-10-17 22:32 ` fxcoudert at gcc dot gnu dot org 2007-10-17 23:49 ` jvdelisle at gcc dot gnu dot org 2007-10-17 23:58 ` kargl at gcc dot gnu dot org 2007-10-18 0:18 ` jvdelisle at gcc dot gnu dot org 2007-10-18 7:38 ` fxcoudert at gcc dot gnu dot org 2007-10-18 18:23 ` burnus at gcc dot gnu dot org 2007-12-08 18:07 ` fxcoudert at gcc dot gnu dot org 2008-02-01 16:59 ` jsm28 at gcc dot gnu dot org 2008-02-01 17:23 ` fxcoudert at gcc dot gnu dot org 2009-07-15 9:41 ` burnus at gcc dot gnu dot org 2009-07-24 8:21 ` burnus at gcc dot gnu dot org 2009-12-05 21:53 ` tkoenig 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=20070205194047.13623.qmail@sourceware.org \ --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).