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 middle-end/111497] [11/12/13/14 Regression] ICE building mariadb on i686 since r8-470
Date: Mon, 25 Sep 2023 20:20:24 +0000	[thread overview]
Message-ID: <bug-111497-4-uazNSA67Uw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111497-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>:

https://gcc.gnu.org/g:3c23defed384cf17518ad6c817d94463a445d21b

commit r14-4256-g3c23defed384cf17518ad6c817d94463a445d21b
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Mon Sep 25 16:19:50 2023 -0400

    [PR111497][LRA]: Copy substituted equivalence

    When we substitute the equivalence and it becomes shared, we can fail
    to correctly update reg info used by LRA.  This can result in wrong
    code generation, e.g. because of incorrect live analysis.  It can also
    result in compiler crash as the pseudo survives RA.  This is what
    exactly happened for the PR.  This patch solves this problem by
    unsharing substituted equivalences.

    gcc/ChangeLog:

            PR middle-end/111497
            * lra-constraints.cc (lra_constraints): Copy substituted
            equivalence.
            * lra.cc (lra): Change comment for calling unshare_all_rtl_again.

    gcc/testsuite/ChangeLog:

            PR middle-end/111497
            * g++.target/i386/pr111497.C: new test.

  parent reply	other threads:[~2023-09-25 20:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 14:35 [Bug middle-end/111497] New: " jakub at gcc dot gnu.org
2023-09-20 14:35 ` [Bug middle-end/111497] " jakub at gcc dot gnu.org
2023-09-20 14:36 ` jakub at gcc dot gnu.org
2023-09-20 14:41 ` jakub at gcc dot gnu.org
2023-09-20 14:55 ` jakub at gcc dot gnu.org
2023-09-22 19:50 ` vmakarov at gcc dot gnu.org
2023-09-25 20:20 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-13 16:17 ` jakub at gcc dot gnu.org
2023-11-13 18:27 ` vmakarov at gcc dot gnu.org
2023-11-30  8:23 ` [Bug middle-end/111497] [11/12/13 " rguenth at gcc dot gnu.org
2023-11-30 11:44 ` cvs-commit at gcc dot gnu.org
2024-06-12 12:33 ` [Bug middle-end/111497] [11/12 " cvs-commit 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-111497-4-uazNSA67Uw@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).