public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30512] MAXVAL() incorrect for zero-size int arrays, and for -HUGE-1 maximum values. Date: Mon, 22 Jan 2007 07:56:00 -0000 [thread overview] Message-ID: <20070122075615.29139.qmail@sourceware.org> (raw) In-Reply-To: <bug-30512-13350@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from fxcoudert at gcc dot gnu dot org 2007-01-22 07:56 ------- I don't think it's a bug, since "the negative number with the largest magnitude possible within the representation" is not -huge()-1, but -huge(). If I understand the standard correctly, -huge()-1, although being representible by the hardware you have, is not "within the representation" of this integer kind, because the range of the representation of an integer kind is supposed to be symmetric. For what it's worth, the Intel and Sun compilers have the behaviour you expect, but the Portland compiler and g95 both have the same behaviour as gfortran. Steve might have an idea on that, IIRC he's the one who implemented the -frange-check option. Otherwise, a question to comp.lang.fortran would be a good thing. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu dot | |org, kargl at gcc dot gnu | |dot org Status|NEW |SUSPENDED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30512
next prev parent reply other threads:[~2007-01-22 7:56 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-20 0:10 [Bug fortran/30512] New: " brooks at gcc dot gnu dot org 2007-01-20 9:38 ` [Bug fortran/30512] " burnus at gcc dot gnu dot org 2007-01-20 12:46 ` burnus at gcc dot gnu dot org 2007-01-22 7:56 ` fxcoudert at gcc dot gnu dot org [this message] 2007-01-22 8:47 ` burnus at gcc dot gnu dot org 2007-01-22 20:16 ` sgk at troutmask dot apl dot washington dot edu 2007-01-27 13:24 ` tkoenig at gcc dot gnu dot org 2007-01-28 22:39 ` tkoenig at gcc dot gnu dot org 2007-01-29 8:40 ` burnus at gcc dot gnu dot org 2007-01-30 17:58 ` burnus at gcc dot gnu dot org 2007-02-01 9:01 ` patchapp at dberlin dot org 2007-02-09 21:56 ` burnus at gcc dot gnu dot org 2007-02-16 14:16 ` [Bug fortran/30512] [4.2, 4.1 only] " burnus at gcc dot gnu dot org 2007-02-16 14:17 ` [Bug fortran/30512] [4.1 " burnus at gcc dot gnu dot org 2007-02-17 21:29 ` tkoenig at gcc dot gnu dot org 2007-02-20 17:39 ` 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=20070122075615.29139.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).