public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99561] gfortran reports an error for a truncation that is permitted by the standard
Date: Fri, 12 Mar 2021 18:39:49 +0000	[thread overview]
Message-ID: <bug-99561-4-skXJMTOJHT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99561-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99561

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Michal Paszta from comment #0)
> In this line of code:
> 
> INTEGER(KIND=1) :: var8 = 257_2
> 
> we try to cast an integer of kind 2 (16 bits) onto an integer of kind 1 (8
> bits, value up to 256). This will result in a truncation of the value and is
> allowed by the Fortran 2018 Standard, see Table 10.9, Fortran 2018 Standard.
> 

The sentence preceding Table 10.9 and the table tell you 
what conversions are allowed and how the conversion is
done via a built-in intrinsic subprogram.

It does tell you anything about an out-of-range value.
In fact, an INTEGER(KIND=1) entity has a range of
[-128,127], so the value of 256 is still out-of-range.

As you have found, gfortran offers a programmer a bullet
to shoot their foot (i.e, the -fno-range-check option).
On most (all?) targets supported by gfortran, you'll get 
two's complement wrap-around semantics.  You do not get
truncation, where I assume you mean that an out-of-range 
value is truncated to -128 or 127 as the situation would
merit (e.g., var8 = 257_2 <-- huge(var8) = 127).

As to the "no warning problem", you did not ask gfortran
to generate warnings.  You can use either the -Wall option
or the -Wconversion option to get a warning when using
the -fno-range-check option.

%gfcx -o z -fno-range-check -Wall a.f90
a.f90:2:33:

    2 |   integer(1), parameter :: var8 = 257_2
      |                                 1
Warning: Conversion from 'INTEGER(2)' to 'INTEGER(1)' at (1) [-Wconversion]

  reply	other threads:[~2021-03-12 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 13:33 [Bug fortran/99561] New: " michal.paszta at mobica dot com
2021-03-12 18:39 ` kargl at gcc dot gnu.org [this message]
2021-03-12 18:51 ` [Bug fortran/99561] " kargl at gcc dot gnu.org
2021-03-12 19:20 ` sgk at troutmask dot apl.washington.edu

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-99561-4-skXJMTOJHT@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).