public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mlwmohawk at gmail 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 15:34:28 +0000	[thread overview]
Message-ID: <bug-101953-4-uTU7AuaF4v@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 #24 from M W <mlwmohawk at gmail dot com> ---
I know it is documented as "undefined," but it is also unexpected without even
a warning. Anyone maintaining code and/or porting to rpi will simply not expect
this behavior. I certainly didn't. I had been using my code for over a decade
and the default casting did the "correct" (expected) thing across many
different platforms.


I'm really not sure how anyone is OK with this behavior. I'm concerned about
the mountains of code out in the real world that may be failing silently. Now
that the RaspberryPI is being used more and more as a drop in replacement for
old x86 servers, this will impact a lot of people.

  parent reply	other threads:[~2021-08-18 15:34 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 [this message]
2021-08-18 20:44 ` joseph at codesourcery dot com
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-uTU7AuaF4v@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).