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 libgomp/97331] New: [nvptx] Provide GCN_NUM_TEAMS/GCN_NUM_THREADS equivalent Date: Thu, 08 Oct 2020 08:40:42 +0000 [thread overview] Message-ID: <bug-97331-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97331 Bug ID: 97331 Summary: [nvptx] Provide GCN_NUM_TEAMS/GCN_NUM_THREADS equivalent Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- When looking at the gcn plugin, there are a number of environment variables that set/limit launch dimensions: ... $ grep getenv libgomp/plugin/plugin-gcn.c | grep NUM const char *x = secure_getenv ("GCN_NUM_TEAMS"); x = secure_getenv ("GCN_NUM_GANGS"); const char *z = secure_getenv ("GCN_NUM_THREADS"); z = secure_getenv ("GCN_NUM_WORKERS"); ... It would be nice to have similar ones for nvptx.
next reply other threads:[~2020-10-08 8:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-08 8:40 vries at gcc dot gnu.org [this message] 2020-10-08 8:50 ` [Bug libgomp/97331] " jakub 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-97331-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).