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/104489] nvptx, sm_53: internal compiler error: in gen_rtx_SUBREG, at emit-rtl.cc:1022
Date: Wed, 23 Feb 2022 07:26:35 +0000	[thread overview]
Message-ID: <bug-104489-4-1nlAqyv6Pb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104489-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:06770148711226ba243b964451dfa8816d5d23e5

commit r12-7357-g06770148711226ba243b964451dfa8816d5d23e5
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Wed Feb 23 07:24:50 2022 +0000

    nvptx: Back-end portion of a fix for PR target/104489.

    This one line fix/tweak is the back-end specific change for a fix for
    PR target/104489, that allows the ISA for GCC's nvptx backend to be bumped
    to sm_53.  The machine-independent middle-end pieces were posted here:
    https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590139.html

    2022-02-23  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            PR target/104489
            * config/nvptx/nvptx.md (*movhf_insn): Add subregs_ok attribute.

  parent reply	other threads:[~2022-02-23  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 15:05 [Bug target/104489] New: " vries at gcc dot gnu.org
2022-02-10 15:18 ` [Bug target/104489] " vries at gcc dot gnu.org
2022-02-11 10:15 ` vries at gcc dot gnu.org
2022-02-11 10:18 ` roger at nextmovesoftware dot com
2022-02-14  9:06 ` burnus at gcc dot gnu.org
2022-02-23  7:26 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-04 15:47 ` 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-104489-4-1nlAqyv6Pb@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).