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/107229] [13 Regression] ICE at -O1 and -Os with "-ftree-vectorize": verify_gimple failed since r13-3219-g25413fdb2ac24933 Date: Thu, 13 Oct 2022 11:11:55 +0000 [thread overview] Message-ID: <bug-107229-4-gQA4wGPZZv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107229-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107229 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andre Simoes Dias Vieira <avieira@gcc.gnu.org>: https://gcc.gnu.org/g:9f0d4adabe2035886a1aa8d2ca990a90de000613 commit r13-3270-g9f0d4adabe2035886a1aa8d2ca990a90de000613 Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Thu Oct 13 12:09:38 2022 +0100 ifcvt: Fix bitpos calculation in bitfield lowering [PR107229] The bitposition calculation for the bitfield lowering in loop if conversion was not taking DECL_FIELD_OFFSET into account, which meant that it would result in wrong bitpositions for bitfields that did not end up having representations starting at the beginning of the struct. gcc/ChangeLog: PR tree-optimization/107229 * tree-if-conv.cc (get_bitfield_rep): Fix bitposition calculation. gcc/testsuite/ChangeLog: * gcc.dg/vect/pr107229-1.c: New test. * gcc.dg/vect/pr107229-2.c: New test. * gcc.dg/vect/pr107229-3.c: New test.
next prev parent reply other threads:[~2022-10-13 11:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-12 7:27 [Bug tree-optimization/107229] New: ICE at -O1 and -Os with "-ftree-vectorize": verify_gimple failed zhendong.su at inf dot ethz.ch 2022-10-12 8:04 ` [Bug tree-optimization/107229] [13 Regression] ICE at -O1 and -Os with "-ftree-vectorize": verify_gimple failed since r13-3219-g25413fdb2ac24933 marxin at gcc dot gnu.org 2022-10-12 9:26 ` avieira at gcc dot gnu.org 2022-10-12 16:23 ` law at gcc dot gnu.org 2022-10-13 9:15 ` marxin at gcc dot gnu.org 2022-10-13 11:11 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-14 7:19 ` rguenth at gcc dot gnu.org 2022-10-14 7:20 ` rguenth at gcc dot gnu.org 2022-10-14 7:27 ` 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-107229-4-gQA4wGPZZv@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).