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/108603] [12 Regression] ICE in output_operand_lossage with SVE and ilp32
Date: Mon, 03 Apr 2023 08:57:54 +0000	[thread overview]
Message-ID: <bug-108603-4-NySIcGWmu0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108603-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Sandiford
<rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:caecd24e230c4727c88ad117bab0342f378e81f7

commit r12-9380-gcaecd24e230c4727c88ad117bab0342f378e81f7
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Mon Apr 3 09:57:07 2023 +0100

    Avoid creating (const (reg ...)) [PR108603]

    convert_memory_address_addr_space_1 has two modes: one in which it
    tries to create a self-contained RTL expression (which might fail)
    and one in which it can emit new instructions where necessary.

    When handling a CONST, the function recurses into the CONST's
    operand and then constifies the result.  But that's only valid if
    the result is still a self-contained expression.  If new instructions
    have been emitted, the expression will refer to the (non-constant)
    results of those instructions.

    In the PR, this caused us to emit a nonsensical (const (reg ...))
    REG_EQUAL note.

    gcc/
            PR tree-optimization/108603
            * explow.cc (convert_memory_address_addr_space_1): Only wrap
            the result of a recursive call in a CONST if no instructions
            were emitted.

    gcc/testsuite/
            PR tree-optimization/108603
            * gcc.target/aarch64/sve/pr108603.c: New test.

    (cherry picked from commit b09dc74801cf4e19bdf5fcd18a5cd53fc9e9ca9a)

  parent reply	other threads:[~2023-04-03  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 18:12 [Bug target/108603] New: [11/12 " acoplan at gcc dot gnu.org
2023-01-31  8:46 ` [Bug target/108603] [12/13 " rguenth at gcc dot gnu.org
2023-02-06 14:23 ` marxin at gcc dot gnu.org
2023-02-09 10:34 ` rsandifo at gcc dot gnu.org
2023-02-21 12:51 ` rguenth at gcc dot gnu.org
2023-03-02 10:30 ` cvs-commit at gcc dot gnu.org
2023-04-03  8:57 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-03  9:02 ` [Bug target/108603] [12 " rsandifo 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-108603-4-NySIcGWmu0@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).