public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/101953] bug on the default cast operator from double to unsigned short
Date: Wed, 18 Aug 2021 20:44:52 +0000	[thread overview]
Message-ID: <bug-101953-4-DfGnwiMQYM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101953-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #25 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The option to use to detect this is -fsanitize=float-cast-overflow (note: 
I haven't tested if it detects this particular case).  As per the manual: 
"Unlike other similar options, @option{-fsanitize=float-cast-overflow} is 
not enabled by @option{-fsanitize=undefined}.".  (Annex F makes the result 
an unspecified value with "invalid" raised, instead of being undefined 
behavior, which justifies not including it in -fsanitize=undefined by 
default.  That means that each time such a conversion occurs in the 
abstract machine, some value representable in the result type must be 
produced; it can't be a "wobbly" value where different uses of the result 
of the conversion, that was only executed once in the abstract machine, 
act like different values or like values not of the result type.  If such 
a conversion does produce a wobbly value, that's a bug; see bug 93806 
comments 27 to 29 for examples of such a bug.)

  parent reply	other threads:[~2021-08-18 20:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 22:19 [Bug c/101953] New: " mlwmohawk at gmail dot com
2021-08-17 22:19 ` [Bug c/101953] " mlwmohawk at gmail dot com
2021-08-17 22:51 ` schwab@linux-m68k.org
2021-08-18  0:32 ` mlwmohawk at gmail dot com
2021-08-18  0:40 ` pinskia at gcc dot gnu.org
2021-08-18  0:41 ` pinskia at gcc dot gnu.org
2021-08-18  1:11 ` mlwmohawk at gmail dot com
2021-08-18  1:12 ` mlwmohawk at gmail dot com
2021-08-18  1:22 ` pinskia at gcc dot gnu.org
2021-08-18  1:23 ` pinskia at gcc dot gnu.org
2021-08-18  1:26 ` pinskia at gcc dot gnu.org
2021-08-18  1:26 ` pinskia at gcc dot gnu.org
2021-08-18  1:32 ` pinskia at gcc dot gnu.org
2021-08-18  1:36 ` pinskia at gcc dot gnu.org
2021-08-18  1:41 ` pinskia at gcc dot gnu.org
2021-08-18  3:01 ` mlwmohawk at gmail dot com
2021-08-18  3:03 ` pinskia at gcc dot gnu.org
2021-08-18  3:05 ` pinskia at gcc dot gnu.org
2021-08-18  3:21 ` mlwmohawk at gmail dot com
2021-08-18  3:37 ` mlwmohawk at gmail dot com
2021-08-18  3:59 ` pinskia at gcc dot gnu.org
2021-08-18  6:02 ` pinskia at gcc dot gnu.org
2021-08-18 12:26 ` harald at gigawatt dot nl
2021-08-18 15:23 ` msebor at gcc dot gnu.org
2021-08-18 15:34 ` mlwmohawk at gmail dot com
2021-08-18 20:44 ` joseph at codesourcery dot com [this message]
2021-08-18 21:59 ` mlwmohawk at gmail dot com
2021-08-18 22:05 ` harald at gigawatt dot nl
2021-08-18 22:12 ` jakub 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-101953-4-DfGnwiMQYM@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).