From: "Liu, Hongtao" <hongtao.liu@intel.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>,
Kirill Yukhin <kirill.yukhin@gmail.com>
Subject: RE: GCC/OpenMP offloading for Intel GPUs?
Date: Wed, 15 Sep 2021 02:00:33 +0000 [thread overview]
Message-ID: <CY4PR11MB2007F2F50F938300A89C3E11E5DB9@CY4PR11MB2007.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87v933nlhn.fsf@dem-tschwing-1.ger.mentorg.com>
I got some feedback from my colleague
-----------------
What we need from GCC
1. generate SPIR-V
2. offload bundler to create FAT object
--------------
If the answer is yes for both, they can hook it up with libomptarget library and our IGC back-end.
>-----Original Message-----
>From: Thomas Schwinge <thomas@codesourcery.com>
>Sent: Wednesday, September 15, 2021 12:57 AM
>To: gcc@gcc.gnu.org
>Cc: Jakub Jelinek <jakub@redhat.com>; Tobias Burnus
><tobias@codesourcery.com>; Kirill Yukhin <kirill.yukhin@gmail.com>; Liu,
>Hongtao <hongtao.liu@intel.com>
>Subject: GCC/OpenMP offloading for Intel GPUs?
>
>Hi!
>
>I've had a person ask about GCC/OpenMP offloading for Intel GPUs (the new
>ones, not MIC, obviously), to complement the existing support for Nvidia and
>AMD GPUs. Is there any statement other than "ought to be doable; someone
>needs to contribute the work"?
>
>
>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 prev parent reply other threads:[~2021-09-15 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 16:57 Thomas Schwinge
2021-09-15 2:00 ` Liu, Hongtao [this message]
2021-09-15 9:19 ` Richard Biener
2021-09-15 9:25 ` Jakub Jelinek
2021-09-15 11:19 ` Thomas Schwinge
2021-09-16 1:40 ` Liu, Hongtao
2021-09-21 10:31 ` Thomas Schwinge
2021-09-21 14:10 ` Tian, Xinmin
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=CY4PR11MB2007F2F50F938300A89C3E11E5DB9@CY4PR11MB2007.namprd11.prod.outlook.com \
--to=hongtao.liu@intel.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=thomas@codesourcery.com \
--cc=tobias@codesourcery.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).