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/106934] [10/11 Regression] ICE: verify_gimple failed since r9-5682-gef310a95a934d0f3
Date: Mon, 17 Oct 2022 13:28:11 +0000 [thread overview]
Message-ID: <bug-106934-4-olBevbwOAe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106934-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106934
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:2bb2560ae196df515cfea9161a27ee86a1594777
commit r11-10318-g2bb2560ae196df515cfea9161a27ee86a1594777
Author: Richard Biener <rguenther@suse.de>
Date: Wed Sep 14 09:00:35 2022 +0200
tree-optimization/106934 - avoid BIT_FIELD_REF of bitfields
The following avoids creating BIT_FIELD_REF of bitfields in
update-address-taken. The patch doesn't implement punning to
a full precision integer type but leaves a comment according to
that.
PR tree-optimization/106934
* tree-ssa.c (non_rewritable_mem_ref_base): Avoid BIT_FIELD_REFs
of bitfields.
(maybe_rewrite_mem_ref_base): Likewise.
* gfortran.dg/pr106934.f90: New testcase.
(cherry picked from commit 05f5c42cb42c5088187d44cc45a5f671d19ad8c5)
next prev parent reply other threads:[~2022-10-17 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 19:32 [Bug fortran/106934] New: [10/11/12/13 Regression] ICE: verify_gimple failed gscfq@t-online.de
2022-09-13 19:44 ` [Bug fortran/106934] " pinskia at gcc dot gnu.org
2022-09-13 20:15 ` [Bug fortran/106934] [10/11/12/13 Regression] ICE: verify_gimple failed since r9-5682-gef310a95a934d0f3 marxin at gcc dot gnu.org
2022-09-14 6:41 ` [Bug tree-optimization/106934] " rguenth at gcc dot gnu.org
2022-09-14 9:57 ` cvs-commit at gcc dot gnu.org
2022-09-14 9:58 ` [Bug tree-optimization/106934] [10/11/12 " rguenth at gcc dot gnu.org
2022-10-11 12:07 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-26 13:05 ` [Bug tree-optimization/106934] [10 " cvs-commit at gcc dot gnu.org
2023-01-26 13:06 ` 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-106934-4-olBevbwOAe@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: link
Be 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).