From: Thomas Schwinge <thomas@codesourcery.com>
To: Tom de Vries <tdevries@suse.de>
Cc: <gcc@gcc.gnu.org>
Subject: nvptx multilib setup (was: [Bug target/104364] [12 Regression] OpenMP/nvptx regressions after "[nvptx] Add some support for .local atomics")
Date: Fri, 4 Feb 2022 08:21:29 +0100 [thread overview]
Message-ID: <87r18jt7uu.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <bug-104364-4-ILKfZXTaRC@http.gcc.gnu.org/bugzilla/>
Hi Tom!
Taking this one to the mailing list; not directly related to PR104364:
On 2022-02-03T13:35:55+0000, "vries at gcc dot gnu.org via Gcc-bugs" <gcc-bugs@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
> I've tested this using (recommended) driver 470.94 on boards:
(As not every user will be using the recommended/latest, I too am doing
some testing also on oldish Nvidia/CUDA Driver versions.) Combinatorial
explosion is a problem, of course...
> while iterating over dimensions { -mptx=3.1 , -mptx=6.3 } x { GOMP_NVPTX_JIT=-O0, <default> }.
Do you use separate (nvptx-none offload target only?) builds for
different '-mptx' variants (likewise: '-misa'), or have you hacked up the
multilib configuration? ('gcc/config/nvptx/t-nvptx:MULTILIB_OPTIONS'
etc., I suppose?) Should we add a few representative configurations to
be built by default? And/or, should we have a way to 'configure' per
user needs (I suppose: '--with-multilib-list=[...]', as supported for a
few other targets?)? (I see there's also a new
'--with-multilib-generator=[...]', haven't looked in detail.) No matter
which way: again, combinatorial explosion is a problem, of course...
For example, in addition to the default (fiji/gfx803) for GCN we've got:
gcc/config/gcn/t-gcn-hsa:MULTILIB_OPTIONS = march=gfx900/march=gfx906/march=gfx908
gcc/config/gcn/t-gcn-hsa:MULTILIB_DIRNAMES = gfx900 gfx906 gfx908
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next parent reply other threads:[~2022-02-04 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-104364-4@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-104364-4-ILKfZXTaRC@http.gcc.gnu.org/bugzilla/>
2022-02-04 7:21 ` Thomas Schwinge [this message]
2022-02-04 12:09 ` Tom de Vries
2022-05-13 14:20 ` nvptx multilib setup Thomas Schwinge
2022-09-28 13:50 ` DejaGnu: flags via 'RUNTESTFLAGS' overriding those specified in test cases Thomas Schwinge
2022-09-28 14:12 ` Jonathan Wakely
2022-09-28 15:39 ` Segher Boessenkool
2022-09-29 8:18 ` Thomas Schwinge
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=87r18jt7uu.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=tdevries@suse.de \
/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).