From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
Uros Bizjak <ubizjak@gmail.com>,
Tom de Vries <tdevries@suse.de>,
Martin Jambor <mjambor@suse.cz>,
gcc-patches@gcc.gnu.org,
Richard Earnshaw <richard.earnshaw@arm.com>,
Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [RFC PATCH] targetm.omp.device_kind_arch_isa and OpenMP declare variant kind/arch/isa handling
Date: Tue, 29 Oct 2019 22:57:00 -0000 [thread overview]
Message-ID: <20191029224011.GH28442@gate.crashing.org> (raw)
In-Reply-To: <20191029171531.GI4650@tucnak>
Hi!
On Tue, Oct 29, 2019 at 06:15:31PM +0100, Jakub Jelinek wrote:
> The standard makes it implementation defined what an arch is and what is
> isa, but I think because there is no selector like target that arch should
> mostly contain identifiers that match the ABI incompatible stuff (target,
> perhaps whether it is 32-bit or 64-bit, plus endianity where needed etc.)
> and keep isa to be identifiers for the ISAs, or perhaps where there are no
> clear ISA names say architecture variants or revisions or similar.
>
> I've only implemented i386 and nvptx so far, will leave the rest to
> port maintainers; would be nice to coordinate what is added a little bit
> with other implementations like LLVM, if they'd be willing to coordinate.
What would this be used for? Can you give some more context?
There already are a lot of different ways to get information about the
execution environment you're running on; why is this any better?
Segher
next prev parent reply other threads:[~2019-10-29 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 17:44 Jakub Jelinek
2019-10-29 22:57 ` Segher Boessenkool [this message]
2019-10-30 3:13 ` Jakub Jelinek
2019-10-30 22:05 ` Segher Boessenkool
2019-10-30 14:20 ` Szabolcs Nagy
2019-10-30 14:51 ` Jakub Jelinek
2019-10-30 17:40 ` Szabolcs Nagy
2019-10-31 9:35 ` Richard Sandiford
2019-10-31 9:39 ` Jakub Jelinek
2019-10-31 10:55 ` Szabolcs Nagy
2019-11-01 17:15 ` Martin Jambor
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=20191029224011.GH28442@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=krebbel@linux.ibm.com \
--cc=mjambor@suse.cz \
--cc=rguenther@suse.de \
--cc=richard.earnshaw@arm.com \
--cc=tdevries@suse.de \
--cc=ubizjak@gmail.com \
/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).