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/114080] Inconsistent handling of unaligned 128bit ints between GCC versions Date: Fri, 23 Feb 2024 15:40:45 +0000 [thread overview] Message-ID: <bug-114080-4-TePx5YHDnL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114080 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The alignment requirement for int128_t has always been 16byte aligned. So if you cast an unaligned pointer to int128_t pointer you run into c undefined behavior. Just happens now gcc will use the sse registers to do things like xor and such and the sse loads trap on unaligned.
next prev parent reply other threads:[~2024-02-23 15:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-23 15:32 [Bug c/114080] New: Inconsistent handling of " rapier at psc dot edu 2024-02-23 15:37 ` [Bug c/114080] Inconsistent handling of unaligned " jakub at gcc dot gnu.org 2024-02-23 15:40 ` pinskia at gcc dot gnu.org [this message] 2024-02-23 15:46 ` jakub at gcc dot gnu.org 2024-02-23 15:48 ` redi at gcc dot gnu.org 2024-02-23 16:04 ` rapier at psc dot edu 2024-02-23 16:08 ` jakub at gcc dot gnu.org 2024-02-23 16:11 ` pinskia at gcc dot gnu.org 2024-02-23 16:36 ` rapier at psc dot edu 2024-02-23 17:14 ` 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-114080-4-TePx5YHDnL@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).