public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	Hongtao Liu <hongtao.liu@intel.com>,
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	Richard Biener <rguenther@suse.de>, Michael Matz <matz@suse.de>,
	Tobias Burnus <tobias@codesourcery.com>
Subject: Re: GCC 13: OpenMP offloading to Intel MIC has been removed (was: Remove support for Intel MIC offloading)
Date: Fri, 4 Nov 2022 11:36:25 +0100	[thread overview]
Message-ID: <Y2TrKWhrEnXHlIuz@tucnak> (raw)
In-Reply-To: <87cza32fxi.fsf@euler.schwinge.homeip.net>

On Fri, Nov 04, 2022 at 11:05:13AM +0100, Thomas Schwinge wrote:
> Hi!
> 
> On 2022-10-20T13:34:41+0200, Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> > we'll need to update the offloading wiki
> 
> I'll look into that.  I assume we just remove any "Intel MIC" text,
> unless historically or otherwise still relevant, of course.

Well, e.g. at the start
GCC 5 and later support two offloading configurations:

    OpenMP to Intel MIC targets (upcoming Intel Xeon Phi products codenamed KNL) as well as MIC emulation on host. 
should be kept, and in the GCC 13 entry say that the support has been
removed.  Or perhaps better split the GCC 5 entry to say that
GCC 5 and later support OpenACC to NVidia PTX and another entry
that GCC 5 to GCC 12 support OpenMP to Intel MIC.

As there is just one wiki for all the GCC versions, I think we
should keep the MIC stuff in there for now but add notes to the various
spots that it isn't there for GCC 13 anymore (repeat the info).
And when GCC 12.5 is released and branch 12 closes we can drop it
except from the first part of the wiki.

	Jakub


  reply	other threads:[~2022-11-04 10:36 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 [this message]
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           ` Remove support for Intel MIC offloading Thomas Schwinge
2022-11-04  9:54             ` 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=Y2TrKWhrEnXHlIuz@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hongtao.liu@intel.com \
    --cc=matz@suse.de \
    --cc=rguenther@suse.de \
    --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).