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 target/99829] MVE: ICE in lra_assign at -O3
Date: Tue, 19 Mar 2024 20:59:11 +0000	[thread overview]
Message-ID: <bug-99829-4-uGeApzKpLZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99829-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC 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:9c91f8a88b2db50c8faf70786d3cef27b39ac9fc

commit r14-9557-g9c91f8a88b2db50c8faf70786d3cef27b39ac9fc
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Tue Mar 19 16:57:11 2024 -0400

    [PR99829][LRA]: Fixing LRA ICE on arm

      LRA removed insn setting equivalence to memory whose output was
    reloaded. This resulted in writing an uninitiated value to the memory
    which triggered assert in LRA code checking the final generated code.
    This patch fixes the problem.  Comment in the patch contains more
    details about the problem and its solution.

    gcc/ChangeLog:

            PR target/99829
            * lra-constraints.cc (lra_constraints): Prevent removing insn
            with reverse equivalence to memory if the memory was reloaded.

  parent reply	other threads:[~2024-03-19 20:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 13:19 [Bug target/99829] New: " acoplan at gcc dot gnu.org
2021-04-13  8:54 ` [Bug target/99829] " acoplan at gcc dot gnu.org
2024-03-12 15:40 ` thiago.bauermann at linaro dot org
2024-03-12 15:47 ` mkuvyrkov at gcc dot gnu.org
2024-03-12 16:16 ` vmakarov at gcc dot gnu.org
2024-03-12 17:03 ` mkuvyrkov at gcc dot gnu.org
2024-03-12 17:35 ` thiago.bauermann at linaro dot org
2024-03-13 15:34 ` vmakarov at gcc dot gnu.org
2024-03-19 20:59 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-28 22:00 ` thiago.bauermann at linaro dot 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-99829-4-uGeApzKpLZ@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).