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/96005] New: Add possibility to use newer ptx isa Date: Tue, 30 Jun 2020 14:36:39 +0000 [thread overview] Message-ID: <bug-96005-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96005 Bug ID: 96005 Summary: Add possibility to use newer ptx isa Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- Currently, we're at ptx isa v3.1: ... static void nvptx_file_start (void) { fputs ("// BEGIN PREAMBLE\n", asm_out_file); fputs ("\t.version\t3.1\n", asm_out_file); ... Using a newer isa could give some benefits, f.i. starting PTX ISA 6.3 we have atom.cas.b16.
next reply other threads:[~2020-06-30 14:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-30 14:36 vries at gcc dot gnu.org [this message] 2020-09-22 8:10 ` [Bug target/96005] " vries at gcc dot gnu.org 2021-05-11 9:23 ` vries at gcc dot gnu.org 2021-05-12 6:12 ` vries at gcc dot gnu.org 2021-05-12 10:59 ` vries at gcc dot gnu.org 2021-05-12 16:38 ` cvs-commit at gcc dot gnu.org 2021-05-12 16:39 ` 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-96005-4@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).