public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jkrahn at nc dot rr dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29471] Warn with -std=f95/f2003 when BOZ is used at invalid places
Date: Fri, 16 Mar 2007 03:54:00 -0000	[thread overview]
Message-ID: <20070316035357.5079.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29471-1719@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from jkrahn at nc dot rr dot com  2007-03-16 03:53 -------
One more comment: I just checked the INT() intrisic for F2003. It actually
still states that a BOZ is initially interpreted as the largest integer type
(ugh!) REAL() has the correct definition of interpreting as the target REAL
kind. I have to assume that they think a LARGE integer will hold all BOZ
values, and can simply be down-cast. Could they actually have forgotten about
negative values?!?

I have not checked F2008 yet. My vote is to just ignore the standards when it
comes to negative BOZ, the way Intel has done it, which I HOPE is what F2008
says.


-- 


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


  parent reply	other threads:[~2007-03-16  3:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14 19:20 [Bug fortran/29471] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-10-16 13:34 ` [Bug fortran/29471] " tobias dot burnus at physik dot fu-berlin dot de
2006-10-16 16:51 ` kargl at gcc dot gnu dot org
2006-10-16 17:12 ` tobias dot burnus at physik dot fu-berlin dot de
2006-10-16 17:23 ` kargl at gcc dot gnu dot org
2007-03-16  3:46 ` jkrahn at nc dot rr dot com
2007-03-16  3:54 ` jkrahn at nc dot rr dot com [this message]
2007-03-16  4:07 ` sgk at troutmask dot apl dot washington dot edu
2007-03-16  4:09 ` sgk at troutmask dot apl dot washington dot edu
2007-03-16  9:45 ` burnus at gcc dot gnu dot org
2007-08-12 20:10 ` fxcoudert at gcc dot gnu dot org
2007-12-08 21:47 ` burnus at gcc dot gnu dot org
2007-12-08 22:08 ` burnus at gcc dot gnu dot org
2007-12-08 22:10 ` burnus at gcc dot gnu dot org
2007-12-11 19:40 ` jkrahn at nc dot rr dot com
2007-12-11 23:15 ` burnus at gcc dot gnu dot org
2007-12-12  1:04 ` jkrahn at nc dot rr dot com

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=20070316035357.5079.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).