public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111882] [13 Regression] : internal compiler error: in get_expr_operand in ifcvt with Variable length arrays and bitfields inside a struct Date: Fri, 03 May 2024 10:10:25 +0000 [thread overview] Message-ID: <bug-111882-4-u1QRiTi4MQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111882-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111882 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Ball <ricbal02@gcc.gnu.org>: https://gcc.gnu.org/g:4950f6bcd3cce9deb630b76af42cd6d6968ba03f commit r13-8678-g4950f6bcd3cce9deb630b76af42cd6d6968ba03f Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Fri Oct 20 17:02:32 2023 +0100 ifcvt: Don't lower bitfields with non-constant offsets [PR 111882] This patch stops lowering of bitfields by ifcvt when they have non-constant offsets as we are not likely to be able to do anything useful with those during vectorization. That also fixes the issue reported in PR 111882, which was being caused by an offset with a side-effect being lowered, but constants have no side-effects so we will no longer run into that problem. gcc/ChangeLog: PR tree-optimization/111882 * tree-if-conv.cc (get_bitfield_rep): Return NULL_TREE for bitfields with non-constant offsets. gcc/testsuite/ChangeLog: * gcc.dg/vect/pr111882.c: New test. (cherry picked from commit 24cf1f600b8ad34c68a51f48884e72d01f729893)
next prev parent reply other threads:[~2024-05-03 10:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 16:32 [Bug c/111882] New: GCC: 14: internal compiler error: in get_expr_operands, at tree-ssa-operands.cc:940 141242068 at smail dot nju.edu.cn 2023-10-19 16:36 ` [Bug tree-optimization/111882] [13/14 Regression] : internal compiler error: in get_expr_operand in ifcvt pinskia at gcc dot gnu.org 2023-10-19 16:39 ` [Bug tree-optimization/111882] [13/14 Regression] : internal compiler error: in get_expr_operand in ifcvt with Variable length arrays inside a struct pinskia at gcc dot gnu.org 2023-10-19 16:43 ` [Bug tree-optimization/111882] [13/14 Regression] : internal compiler error: in get_expr_operand in ifcvt with Variable length arrays and bitfields " pinskia at gcc dot gnu.org 2023-10-20 6:49 ` rguenth at gcc dot gnu.org 2023-10-20 9:55 ` avieira at gcc dot gnu.org 2023-10-20 16:03 ` cvs-commit at gcc dot gnu.org 2024-04-30 16:50 ` [Bug tree-optimization/111882] [13 " avieira at gcc dot gnu.org 2024-05-02 21:22 ` ricbal02 at gcc dot gnu.org 2024-05-03 10:10 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-08 12:48 ` rguenth 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-111882-4-u1QRiTi4MQ@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).