From: Thomas Schwinge <thomas@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Remove support for Intel MIC offloading
Date: Thu, 20 Oct 2022 22:56:57 +0200 [thread overview]
Message-ID: <878rladxie.fsf@dem-tschwing-1.ger.mentorg.com> (raw)
In-Reply-To: <87a65qhhk0.fsf@euler.schwinge.homeip.net>
Hi Jakub, Tobias!
On 2022-10-20T13:15:43+0200, I wrote:
> I'm proposing the attached "Remove support for Intel MIC offloading"
Can you please confirm:
> --- a/gcc/config/i386/i386-options.cc
> +++ b/gcc/config/i386/i386-options.cc
> @@ -307,10 +307,6 @@ ix86_omp_device_kind_arch_isa (enum omp_device_kind_arch_isa trait,
> case omp_device_kind:
> return strcmp (name, "cpu") == 0;
> case omp_device_arch:
> -#ifdef ACCEL_COMPILER
> - if (strcmp (name, "intel_mic") == 0)
> - return 1;
> -#endif
> if (strcmp (name, "x86") == 0)
> return 1;
> if (TARGET_64BIT)
Only remove this bit as quoted, or actually remove the whole function
(used for 'gcc/config/i386/i386.cc:TARGET_OMP_DEVICE_KIND_ARCH_ISA')?
But if I do the latter, I get a few FAILs in compiler-side
'[...]/gomp/declare-variant-[...]' test cases, and
'libgomp.c/declare-variant-1.c'.
You, Jakub, had originally added that in
Subversion r277662 (Git commit 9ba66bf5b9c69e0e2bcd1b2ab88160bf9b2aa417)
"targetm.omp.device_kind_arch_isa and OpenMP declare variant kind/arch/isa handling".
Reading these emails, and the discussion in
<https://gcc.gnu.org/PR105640>
"[OpenMP] Context selectors missing for PowerPC", I infer that we
generally would like to keep this stuff, for non-offloading OpenMP use,
and thus indeed just remove the Intel MIC parts (as quoted above).
Thus:
> --- a/libgomp/libgomp.texi
> +++ b/libgomp/libgomp.texi
> @@ -4303,10 +4303,6 @@ offloading devices (it's not clear if they should be):
>
> @multitable @columnfractions .60 .10 .25
> @headitem @code{arch} @tab @code{kind} @tab @code{isa}
> -@item @code{intel_mic}, @code{x86}, @code{x86_64}, @code{i386}, @code{i486},
> - @code{i586}, @code{i686}, @code{ia32}
> - @tab @code{host}
> - @tab See @code{-m...} flags in ``x86 Options'' (without @code{-m})
> @item @code{amdgcn}, @code{gcn}
> @tab @code{gpu}
> @tab See @code{-march=} in ``AMD GCN Options''
..., I should also restore this, and only remove the Intel MIC mention.
On the other hand:
> diff --git a/gcc/config/i386/t-omp-device b/gcc/config/i386/t-omp-device
> deleted file mode 100644
| index cfb41ed71ce..00000000000
| --- gcc/config/i386/t-omp-device
| +++ /dev/null
| @@ -1,6 +0,0 @@
| -omp-device-properties-i386: $(srcdir)/config/i386/i386-options.cc
| - echo kind: cpu > $@
| - echo arch: intel_mic x86 x86_64 i386 i486 i586 i686 ia32 >> $@
| - echo isa: sse4 `sed -n '/^static struct ix86_target_opts isa2\?_opts\[\] =/,/^};/p' \
| - $(srcdir)/config/i386/i386-options.cc | \
| - sed -n 's/",.*$$//;s/^ { "-m//p'` >> $@
Indeed remove this whole file, or just Intel MIC, again? Here, as I
understand, this is fine to remove completely, as is only used if there
is an actual offload compiler (which now there isn't anymore); unused as
of here:
> --- a/gcc/configure.ac
> +++ b/gcc/configure.ac
> @@ -1153,10 +1147,6 @@ for tgt in `echo $enable_offload_targets | sed 's/,/ /g'`; do
>
> enable_offloading=1
> case "$tgt" in
> - *-intelmic-* | *-intelmicemul-*)
> - omp_device_property=omp-device-properties-i386
> - omp_device_property_tmake_file="${omp_device_property_tmake_file} \$(srcdir)/config/i386/t-omp-device"
> - ;;
> amdgcn*)
> omp_device_property=omp-device-properties-gcn
> omp_device_property_tmake_file="${omp_device_property_tmake_file} \$(srcdir)/config/gcn/t-omp-device"
So I assume that is OK the way I had it prepared.
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:[~2022-10-20 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:45 [PATCH] Remove dead code Martin Liška
2021-11-08 8:59 ` Jakub Jelinek
2021-11-08 14:19 ` Jeff Law
2021-11-12 14:27 ` Martin Liška
2021-11-12 14:41 ` H.J. Lu
2021-11-12 14:44 ` Martin Liška
2021-11-12 15:00 ` H.J. Lu
2021-11-12 19:14 ` Richard Biener
2021-11-12 19:18 ` H.J. Lu
2021-11-12 19:52 ` Richard Biener
2022-10-20 11:15 ` Remove support for Intel MIC offloading (was: [PATCH] Remove dead code.) Thomas Schwinge
2022-10-20 11:34 ` Jakub Jelinek
2022-11-04 10:05 ` GCC 13: OpenMP offloading to Intel MIC has been removed (was: Remove support for Intel MIC offloading) Thomas Schwinge
2022-11-04 10:36 ` Jakub Jelinek
2022-10-20 12:33 ` Remove support for Intel MIC offloading (was: [PATCH] Remove dead code.) Michael Matz
2022-10-20 12:40 ` Jakub Jelinek
2022-10-20 13:09 ` Richard Biener
2023-02-01 15:12 ` Martin Jambor
2023-02-02 21:13 ` GSoC project idea: Separate Host Process Offloading (was: Remove support for Intel MIC offloading) Thomas Schwinge
2023-02-07 23:26 ` GSoC project idea: Separate Host Process Offloading Thomas Schwinge
2023-02-08 7:47 ` Tobias Burnus
2022-10-20 20:56 ` Thomas Schwinge [this message]
2022-11-04 9:54 ` Remove support for Intel MIC offloading Thomas Schwinge
2022-11-04 10:30 ` Jakub Jelinek
2022-11-04 10:35 ` 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=878rladxie.fsf@dem-tschwing-1.ger.mentorg.com \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).