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/104489] nvptx, sm_53: internal compiler error: in gen_rtx_SUBREG, at emit-rtl.cc:1022
Date: Mon, 14 Feb 2022 09:06:02 +0000	[thread overview]
Message-ID: <bug-104489-4-OAcM3VHE7O@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

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

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

--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Roger Sayle from comment #3)
> Patch proposed:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590139.html

which is the machine-independent part. The associated nvptx patch (also by
Roger) is at
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590250.html

  parent reply	other threads:[~2022-02-14  9:06 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 [this message]
2022-02-23  7:26 ` cvs-commit at gcc dot gnu.org
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-OAcM3VHE7O@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).