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/115552] wrong code at -O2 and above when strict-aliasing with uint128 and double Date: Wed, 19 Jun 2024 22:13:13 +0000 [thread overview] Message-ID: <bug-115552-4-AXZmy9nMkv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115552-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115552 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So basically since main writes via a double type but then spookyhash_short reads via a uint64_t type there is an alias violation. Using an union to change the pointer type does not change there is an alias violation happening. You need to use memcpy for copying from one type to another in this case. Instead of doing: c += u.p64[0]; You could do load_64(&u.p64[0]) and have load_64 defined to be: ``` static inline uint64_t load_64(void *a) { uint64_t t; memcpy(&t, a, sizeof(t)); return t; } ```
next prev parent reply other threads:[~2024-06-19 22:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-19 17:42 [Bug c/115552] New: " davidhu0903ex3 at gmail dot com 2024-06-19 17:48 ` [Bug c/115552] " pinskia at gcc dot gnu.org 2024-06-19 22:13 ` pinskia at gcc dot gnu.org [this message] 2024-06-21 15:02 ` davidhu0903ex3 at gmail dot com
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-115552-4-AXZmy9nMkv@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).