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 rtl-optimization/112875] [14 Regression] ICE: in lra_eliminate_regs_1, at lra-eliminations.cc:670 with -Oz -frounding-math -fno-dce -fno-trapping-math -fno-tree-dce -fno-tree-dse -g
Date: Fri, 08 Dec 2023 20:52:06 +0000	[thread overview]
Message-ID: <bug-112875-4-2A0IKEV0E1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112875-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:48cb51827c9eb991b92014a3f59d31eb237ce03f

commit r14-6347-g48cb51827c9eb991b92014a3f59d31eb237ce03f
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Fri Dec 8 15:37:42 2023 -0500

    [PR112875][LRA]: Fix an assert in lra elimination code

    PR112875 test ran into a wrong assert (gcc_unreachable) in elimination
    in a debug insn.  The insn seems ok.  So I change the assertion.
    To be more accurate I made it the same as analogous reload pass code.

    gcc/ChangeLog:

            PR rtl-optimization/112875
            * lra-eliminations.cc (lra_eliminate_regs_1): Change an assert.
            Add ASM_OPERANDS case.

    gcc/testsuite/ChangeLog:

            PR rtl-optimization/112875
            * gcc.target/i386/pr112875.c: New test.

  parent reply	other threads:[~2023-12-08 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  6:46 [Bug debug/112875] New: " iamanonymous.cs at gmail dot com
2023-12-06  8:02 ` [Bug rtl-optimization/112875] [14 Regression] " rguenth at gcc dot gnu.org
2023-12-08 16:14 ` jakub at gcc dot gnu.org
2023-12-08 19:32 ` vmakarov at gcc dot gnu.org
2023-12-08 20:52 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-06 15:30 ` 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-112875-4-2A0IKEV0E1@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).