public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18026] boz initialization of REALs fails
Date: Mon, 02 Oct 2006 16:47:00 -0000 [thread overview]
Message-ID: <20061002164715.867.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18026-6318@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from kargl at gcc dot gnu dot org 2006-10-02 16:47 -------
Remove reject-valid keyword, again!
Return this to enhancement.
This is NOT a bug. g77 compatibility and the Fortran 95 standard
have a conflict, and so IMNSHO the Fortran 95 standard wins.
See comment #3. The Fortran 95 standard has quite explicit language
concerning how a BOZ is handled in a DATA statement, and that is what
gfortran implements. A BOZ is handled consistently so that the
gfortran extension of allowing a BOZ in an assignment gives the same
result as the DATA statement.
troutmask:kargl[204] cat a.f90
PROGRAM GFCBUG19
DOUBLE PRECISION y, x
DATA x / Z'7FF0000000000000' / ! Conforms to Fortran 95 standard
y = Z'7FF0000000000000' ! gfortran extension
print *, x, y
END
troutmask:kargl[205] gfc -o z a.f90
troutmask:kargl[206] ./z
9.218868437227405E+018 9.218868437227405E+018
If someone wants to create a patch to implement a -fbroken-boz-behavior
option, then that's fine. OTOH, the user can use the bit manipulation
functions and TRANSFER to create whatever bit pattern the user wants.
Or, the user can use the -fno-range-check option and simply compute
inf = 1./0. and nan = 0. / .0.
--
kargl at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu dot org
Severity|normal |enhancement
Keywords|rejects-valid |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18026
next prev parent reply other threads:[~2006-10-02 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18026-6318@http.gcc.gnu.org/bugzilla/>
2006-05-12 13:05 ` guilloteau at obs dot u-bordeaux1 dot fr
2006-05-12 17:43 ` kargl at gcc dot gnu dot org
2006-10-02 11:09 ` fxcoudert at gcc dot gnu dot org
2006-10-02 16:47 ` kargl at gcc dot gnu dot org [this message]
2006-10-02 21:35 ` anlauf at gmx dot de
2006-10-03 1:48 ` sgk at troutmask dot apl dot washington dot edu
2006-10-23 17:10 ` kargl at gcc dot gnu dot org
2006-10-23 18:52 ` tobias dot burnus at physik dot fu-berlin dot de
2006-10-23 19:39 ` sgk at troutmask dot apl dot washington dot edu
2007-08-06 17:30 ` kargl at gcc dot gnu dot org
2007-08-06 17:33 ` kargl at gcc dot gnu dot org
2007-12-08 21:47 ` burnus at gcc dot gnu dot org
2007-12-08 22:09 ` burnus at gcc dot gnu dot org
[not found] <bug-18026-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:16 ` jackie.rosen at hushmail dot com
[not found] <20041015213354.18026.anlauf@gmx.de>
2005-07-26 13:04 ` pinskia at gcc dot gnu dot org
2004-10-15 21:33 [Bug fortran/18026] New: gfortran: regression w.r.t. g77, lacks -ftypeless-boz anlauf at hep dot tu-darmstadt dot de
2005-03-13 19:05 ` [Bug fortran/18026] boz initialization of REALs fails tobi at gcc dot gnu dot org
2005-03-15 21:05 ` kargl 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=20061002164715.867.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: 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).