public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58204] Spurious error when using BOZ literal to set an integer
Date: Tue, 03 Sep 2013 15:25:00 -0000 [thread overview]
Message-ID: <bug-58204-4-X27WvZWVR2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58204-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58204
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-09-03
CC| |burnus at gcc dot gnu.org,
| |sgk at troutmask dot apl.washingto
| |n.edu
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
After knotting my neurons over the f2008 standard and their extracts in this PR
and PR54072, I think the current implementation (r202213) is valid for f95, but
does not handle the way it should be interpreted for more recent standards, at
least for f2008 (did not checked f2003).
Concerning the sign bit, i.e., "The interpretation of a bit sequence whose most
significant bit is 1 is processor dependent.", I think it does not make sense
to reject it (does anyone knows a present piece of hardware which is not using
two's complement?).
next prev parent reply other threads:[~2013-09-03 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 16:21 [Bug fortran/58204] New: " quantheory at gmail dot com
2013-09-03 15:25 ` dominiq at lps dot ens.fr [this message]
2013-09-04 2:38 ` [Bug fortran/58204] [F2008] BOZ literals in the int function should not be treated as unsigned integers quantheory at gmail dot com
2013-09-04 3:45 ` kargl at gcc dot gnu.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-58204-4-X27WvZWVR2@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).