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/110332] [14 regression] ICE in dominated_by_p when building LLVM with -O3
Date: Thu, 22 Jun 2023 08:14:21 +0000	[thread overview]
Message-ID: <bug-110332-4-iGShvT61Ud@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110332-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110332

--- Comment #11 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:2ac41866270e9fbab504bbda7a942a97abaa203a

commit r14-2031-g2ac41866270e9fbab504bbda7a942a97abaa203a
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Jun 22 09:04:01 2023 +0200

    tree-optimization/110332 - fix ICE with phiprop

    The following fixes an ICE that occurs when we visit an edge
    inserted load from the code validating correctness for inserting
    an aggregate copy there.  We can simply skip those loads here.

            PR tree-optimization/110332
            * tree-ssa-phiprop.cc (propagate_with_phi): Always
            check aliasing with edge inserted loads.

            * g++.dg/torture/pr110332.C: New testcase.
            * gcc.dg/torture/pr110332-1.c: Likewise.
            * gcc.dg/torture/pr110332-2.c: Likewise.

  parent reply	other threads:[~2023-06-22  8:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  4:57 [Bug tree-optimization/110332] New: " sjames at gcc dot gnu.org
2023-06-21  4:59 ` [Bug tree-optimization/110332] " sjames at gcc dot gnu.org
2023-06-21  5:00 ` pinskia at gcc dot gnu.org
2023-06-21  5:07 ` pinskia at gcc dot gnu.org
2023-06-21  5:19 ` pinskia at gcc dot gnu.org
2023-06-21  8:36 ` rguenth at gcc dot gnu.org
2023-06-21 16:57 ` sjames at gcc dot gnu.org
2023-06-21 17:05 ` slyfox at gcc dot gnu.org
2023-06-21 17:11 ` pinskia at gcc dot gnu.org
2023-06-21 20:55 ` pinskia at gcc dot gnu.org
2023-06-22  6:08 ` slyfox at gcc dot gnu.org
2023-06-22  6:40 ` rguenth at gcc dot gnu.org
2023-06-22  8:14 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-22  8:14 ` rguenth at gcc dot gnu.org
2023-06-22  9:55 ` slyfox 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-110332-4-iGShvT61Ud@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).