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/105971] [12 Regression] ICE in bitmap_check_index, at sbitmap.h:104
Date: Tue, 19 Jul 2022 11:38:14 +0000 [thread overview]
Message-ID: <bug-105971-4-9mIuQh3NSD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105971-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105971
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:8dd1c404ec77c6d2cdaaf93d219e3250081355c0
commit r12-8580-g8dd1c404ec77c6d2cdaaf93d219e3250081355c0
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jun 15 11:27:31 2022 +0200
tree-optimization/105971 - less surprising refs_may_alias_p_2
When DSE asks whether __real a is using __imag a it gets a surprising
result when a is a FUNCTION_DECL. The following makes sure this case
is less surprising to callers but keeping the bail-out for the
non-decl case where it is true that PTA doesn't track aliases to code
correctly.
2022-06-15 Richard Biener <rguenther@suse.de>
PR tree-optimization/105971
* tree-ssa-alias.cc (refs_may_alias_p_2): Put bail-out for
FUNCTION_DECL and LABEL_DECL refs after decl-decl disambiguation
to leak less surprising alias results.
* gcc.dg/torture/pr106971.c: New testcase.
(cherry picked from commit 8c2733e16ec1c0cdda3db4cdc5ad158a96a658e8)
next prev parent reply other threads:[~2022-07-19 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 10:26 [Bug c/105971] New: [12/13 " gscfq@t-online.de
2022-06-15 8:55 ` [Bug tree-optimization/105971] " rguenth at gcc dot gnu.org
2022-06-15 9:27 ` rguenth at gcc dot gnu.org
2022-06-15 11:15 ` cvs-commit at gcc dot gnu.org
2022-06-15 11:16 ` [Bug tree-optimization/105971] [12 " rguenth at gcc dot gnu.org
2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-19 11:40 ` 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-105971-4-9mIuQh3NSD@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).