public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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 01:32:04 +0000 [thread overview] Message-ID: <bug-101953-4-QMkLkrHQdI@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 #12 from Andrew Pinski <pinskia at gcc dot gnu.org> --- For aarch64 we do: fcvtzs w0, d0 ; int fcvtzu w0, d0 ; uint32_t For ARM: vcvt.s32.f64 s15, d16 ; int vcvt.u32.f64 s15, d7 ; uint32_t For x86 we do: cvttsd2sil %xmm0, %eax ; int cvttsd2siq %xmm0, %rax ;unsigned int 32 So in the case of x86, we convert it to long long and then truncate while on aarch64/arm, it is a direct conversion. This is because on x86 there is no instruction which does unsigned; only signed.
next prev parent reply other threads:[~2021-08-18 1:32 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 [this message] 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 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-QMkLkrHQdI@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: linkBe 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).