public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112313] [14 Regression] GCN target 'gcc.dg/pr111082.c' ICE, 'during RTL pass: vregs': 'error: unrecognizable insn'
Date: Fri, 10 Nov 2023 10:40:30 +0000	[thread overview]
Message-ID: <bug-112313-4-x6kB3wkMzR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112313-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

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

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Fix written and committed by Andrew as r14-5316-g8da8b922576212

"The problem was a missed case in the vector reduction expand code."

See also https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635982.html


commit 8da8b9225762126ca41b12243d6531cd41a831b3
Author: Andrew Stubbs <ams@codesourcery.com>
Date:   Fri Nov 10 09:43:21 2023 +0000

    amdgcn: Fix vector min/max ICE

    The DImode min/max instructions need a clobber that SImode does not, so
    add the special case to the reduction expand code.

    gcc/ChangeLog:

            * config/gcn/gcn.cc (gcn_expand_reduc_scalar): Add clobber to
DImode
            min/max instructions.

  parent reply	other threads:[~2023-11-10 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 11:54 [Bug target/112313] New: " tschwinge at gcc dot gnu.org
2023-11-02  8:26 ` [Bug target/112313] " rguenth at gcc dot gnu.org
2023-11-10 10:40 ` burnus at gcc dot gnu.org [this message]
2023-11-10 10:47 ` ams 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-112313-4-x6kB3wkMzR@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).