public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries 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: Fri, 11 Feb 2022 10:15:25 +0000 [thread overview] Message-ID: <bug-104489-4-584rjdo87n@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 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- Minimal reproducer: ... typedef float HFtype __attribute__ ((mode (HF))); HFtype mulhf (HFtype a, HFtype b) { return a * b; } ...
next prev parent reply other threads:[~2022-02-11 10:15 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 [this message] 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 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-584rjdo87n@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: linkBe 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).