public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113201] [14 Regression] internal compiler error: tree check: expected ssa_name, have integer_cst in replace_uses_by, at tree-cfg.cc:2058
Date: Wed, 03 Jan 2024 17:47:27 +0000	[thread overview]
Message-ID: <bug-113201-4-egMbUm1KT2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113201-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 56986
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56986&action=edit
gcc14-pr113201.patch

So, do we want just avoid trying to propagate constants to rslt uses if it is
used in abnormal PHI like in this patch, or punt on doing final value
replacement in that case altogether?

  parent reply	other threads:[~2024-01-03 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 15:48 [Bug middle-end/113201] New: " doko at gcc dot gnu.org
2024-01-02 21:39 ` [Bug tree-optimization/113201] " pinskia at gcc dot gnu.org
2024-01-02 21:43 ` pinskia at gcc dot gnu.org
2024-01-03 17:47 ` jakub at gcc dot gnu.org [this message]
2024-01-05 10:18 ` cvs-commit at gcc dot gnu.org
2024-01-05 10:19 ` jakub at gcc dot gnu.org
2024-01-05 14:20 ` jakub 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-113201-4-egMbUm1KT2@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).