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/13 Regression] ICE in bitmap_check_index, at sbitmap.h:104 Date: Wed, 15 Jun 2022 11:15:28 +0000 [thread overview] Message-ID: <bug-105971-4-CdDHu6JgTX@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 #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:8c2733e16ec1c0cdda3db4cdc5ad158a96a658e8 commit r13-1106-g8c2733e16ec1c0cdda3db4cdc5ad158a96a658e8 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.
next prev parent reply other threads:[~2022-06-15 11:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-14 10:26 [Bug c/105971] New: " 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 [this message] 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 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-CdDHu6JgTX@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).