public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111015] [11/12/13/14 Regression] __int128 bitfields optimized incorrectly to the 64 bit operations Date: Wed, 16 Aug 2023 15:14:44 +0000 [thread overview] Message-ID: <bug-111015-4-94pF7YaSn7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111015-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111015 --- Comment #4 from Mikael Pettersson <mikpelinux at gmail dot com> --- Reverting the pass_store_merging::process_store hunk makes this test case work again: diff --git a/gcc/gimple-ssa-store-merging.cc b/gcc/gimple-ssa-store-merging.cc index 0d19b98ed73..c4bf8eec64e 100644 --- a/gcc/gimple-ssa-store-merging.cc +++ b/gcc/gimple-ssa-store-merging.cc @@ -5299,7 +5299,7 @@ pass_store_merging::process_store (gimple *stmt) && bitsize.is_constant (&const_bitsize) && ((const_bitsize % BITS_PER_UNIT) != 0 || !multiple_p (bitpos, BITS_PER_UNIT)) - && const_bitsize <= MAX_FIXED_MODE_SIZE) + && const_bitsize <= 64) { /* Bypass a conversion to the bit-field type. */ if (!bit_not_p
next prev parent reply other threads:[~2023-08-16 15:14 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-14 13:53 [Bug rtl-optimization/111015] New: " pshevchuk at pshevchuk dot com 2023-08-14 14:01 ` [Bug rtl-optimization/111015] " rguenth at gcc dot gnu.org 2023-08-14 14:04 ` [Bug tree-optimization/111015] [11/12/13/14 Regression] " rguenth at gcc dot gnu.org 2023-08-15 23:06 ` mikpelinux at gmail dot com 2023-08-16 15:14 ` mikpelinux at gmail dot com [this message] 2023-08-29 12:41 ` jakub at gcc dot gnu.org 2023-08-29 14:24 ` jakub at gcc dot gnu.org 2023-08-30 8:47 ` cvs-commit at gcc dot gnu.org 2023-08-30 9:33 ` cvs-commit at gcc dot gnu.org 2023-08-30 9:49 ` cvs-commit at gcc dot gnu.org 2023-08-30 9:57 ` cvs-commit at gcc dot gnu.org 2023-08-30 10:00 ` 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-111015-4-94pF7YaSn7@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).