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/104440] nvptx: FAIL: gcc.c-torture/execute/pr53465.c execution test
Date: Tue, 08 Feb 2022 08:07:54 +0000 [thread overview]
Message-ID: <bug-104440-4-0ftFMqgBJ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104440-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |nvptx
Keywords| |testsuite-fail
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Tentative patch that fixes example:
...
diff --git a/gcc/config/nvptx/nvptx.cc b/gcc/config/nvptx/nvptx.cc
index 5b26c0f4c7dd..4dc154434853 100644
--- a/gcc/config/nvptx/nvptx.cc
+++ b/gcc/config/nvptx/nvptx.cc
@@ -1565,6 +1565,23 @@ nvptx_declare_function_name (FILE *file, const char
*name, cons
t_tree decl)
fprintf (file, "\t.reg%s ", nvptx_ptx_type_from_mode (mode, true));
output_reg (file, i, split, -2);
fprintf (file, ";\n");
+ switch (mode)
+ {
+ case HImode:
+ fprintf (file, "\tmov.u16 %%r%d, 0;\n", i);
+ break;
+ case SImode:
+ fprintf (file, "\tmov.u32 %%r%d, 0;\n", i);
+ break;
+ case DImode:
+ fprintf (file, "\tmov.u64 %%r%d, 0;\n", i);
+ break;
+ case BImode:
+ fprintf (file, "\tsetp.ne.u32 %%r%d,0,0;\n", i);
+ break;
+ default:
+ gcc_unreachable ();
+ }
}
}
...
next prev parent reply other threads:[~2022-02-08 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 8:06 [Bug target/104440] New: " vries at gcc dot gnu.org
2022-02-08 8:07 ` vries at gcc dot gnu.org [this message]
2022-02-08 8:09 ` [Bug target/104440] " pinskia at gcc dot gnu.org
2022-02-08 8:11 ` pinskia at gcc dot gnu.org
2022-02-08 8:16 ` vries at gcc dot gnu.org
2022-02-08 8:22 ` pinskia at gcc dot gnu.org
2022-02-08 9:25 ` rguenth at gcc dot gnu.org
2022-02-08 9:26 ` rguenth at gcc dot gnu.org
2022-02-17 7:20 ` vries at gcc dot gnu.org
2022-02-17 7:37 ` vries at gcc dot gnu.org
2022-02-17 7:58 ` vries at gcc dot gnu.org
2022-02-20 22:48 ` vries at gcc dot gnu.org
2022-02-21 15:51 ` cvs-commit at gcc dot gnu.org
2022-02-21 15:52 ` vries 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-104440-4-0ftFMqgBJ3@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).