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 tree-optimization/108199] Bitfields, unions and SRA and storage_order_attribute Date: Thu, 22 Dec 2022 16:39:28 +0000 [thread overview] Message-ID: <bug-108199-4-ktxn8BD36P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108199-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108199 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-12-22 Summary|Bitfields and |Bitfields, unions and SRA |storage_order_attribute |and storage_order_attribute Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Andreas Krebbel from comment #2) > The problem appears to get introduced when dead store elimination removes > the assignment to the target struct in FRE. There is no DSE in FRE going on .... Rather SRA did messed up. > > Before FRE we have the following: > > _1 = src_6(D)->a; bswap > dst$val_9 = _1; bswap > _2 = BIT_FIELD_REF <dst$val_9, 8, 0>; bswap > _3 = _2 & 64; > if (_3 != 0) dst$val_9/_1 are both SSA names and not a store/load. so there is no swapping going on. It is definitely SRA going wrong. Turning off SRA (-fno-sra) and we get the correct thing at the end.
next prev parent reply other threads:[~2022-12-22 16:39 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-22 16:08 [Bug tree-optimization/108199] New: Bitfields " krebbel at gcc dot gnu.org 2022-12-22 16:09 ` [Bug tree-optimization/108199] " krebbel at gcc dot gnu.org 2022-12-22 16:24 ` krebbel at gcc dot gnu.org 2022-12-22 16:29 ` krebbel at gcc dot gnu.org 2022-12-22 16:39 ` pinskia at gcc dot gnu.org [this message] 2022-12-22 17:08 ` [Bug tree-optimization/108199] Bitfields, unions and SRA " krebbel at gcc dot gnu.org 2022-12-22 18:29 ` pinskia at gcc dot gnu.org 2022-12-23 7:53 ` krebbel at gcc dot gnu.org 2023-01-09 13:21 ` rguenth at gcc dot gnu.org 2023-01-09 20:15 ` ebotcazou at gcc dot gnu.org 2023-01-09 20:26 ` pinskia at gcc dot gnu.org 2023-01-09 21:46 ` ebotcazou at gcc dot gnu.org 2023-01-10 11:11 ` ebotcazou at gcc dot gnu.org 2023-01-10 11:24 ` ebotcazou at gcc dot gnu.org 2023-01-11 15:03 ` cvs-commit at gcc dot gnu.org 2023-01-11 15:35 ` krebbel at gcc dot gnu.org 2023-01-11 15:41 ` krebbel at gcc dot gnu.org 2023-01-11 16:11 ` ebotcazou at gcc dot gnu.org 2023-01-11 19:46 ` cvs-commit at gcc dot gnu.org 2023-01-11 19:47 ` cvs-commit at gcc dot gnu.org 2023-01-11 19:48 ` ebotcazou 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-108199-4-ktxn8BD36P@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).