From: LIU Hao <lh_mouse@126.com>
To: Xi Ruoyao <xry111@xry111.site>,
Alexander Monakov <amonakov@ispras.ru>,
stefan@franke.ms
Cc: gcc-help@gcc.gnu.org
Subject: Re: optimizer discards sign information
Date: Wed, 10 Apr 2024 17:40:13 +0800 [thread overview]
Message-ID: <0c105596-ecca-4936-84b0-b2f081b47bf2@126.com> (raw)
In-Reply-To: <5379650ad2582ae97c40ef1a78ded354033d2f71.camel@xry111.site>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
在 2024-04-10 17:19, Xi Ruoyao via Gcc-help 写道:
> $ cc t.c -O2 -fsanitize=undefined
> $ ./a.out
> t.c:7:15: runtime error: signed integer overflow: 65535 * 65535 cannot be represented in type 'int'
> fffe0001
Undefined behavior is not a valid point, as it never happens. It's a real bug. There are many PRs on
bugzilla.
The sign extension could have been eliminated completely:
movzx eax, si
movzx edi, di
imul eax, edi
ret
And here is a similar issue:
typedef unsigned long long int u64;
typedef unsigned int u32;
u64 foo(u64 a) {
return (u32) __builtin_ctzll(a);
}
which results in
xor eax, eax
rep bsf rax, rdi // effectively `tzcnt rax, rdi`
cdqe // unnecessary sign-extension
ret
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-04-10 9:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 8:52 stefan
2024-04-10 9:16 ` Alexander Monakov
2024-04-10 9:19 ` Xi Ruoyao
2024-04-10 9:40 ` LIU Hao [this message]
2024-04-10 9:44 ` Xi Ruoyao
2024-04-10 9:51 ` LIU Hao
2024-04-10 9:52 ` Xi Ruoyao
2024-04-10 10:07 ` LIU Hao
2024-04-10 10:17 ` Xi Ruoyao
2024-04-10 10:03 ` AW: " stefan
2024-04-10 10:34 ` Xi Ruoyao
2024-04-10 9:24 ` stefan
2024-04-10 9:49 ` stefan
2024-04-10 9:54 ` Xi Ruoyao
2024-04-10 9:57 ` LIU Hao
2024-04-10 10:03 ` Xi Ruoyao
2024-04-10 11:52 ` David Brown
2024-04-10 14:25 ` Stefan Franke
2024-04-10 16:51 ` David Brown
2024-04-11 0:32 ` Oleg Endo
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=0c105596-ecca-4936-84b0-b2f081b47bf2@126.com \
--to=lh_mouse@126.com \
--cc=amonakov@ispras.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=stefan@franke.ms \
--cc=xry111@xry111.site \
/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).