From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>, hjl.tools@gmail.com
Cc: gcc-patches@gcc.gnu.org, Tobias Burnus <tobias@codesourcery.com>
Subject: Re: [PATCH] Remove dead code.
Date: Mon, 8 Nov 2021 09:59:18 +0100 [thread overview]
Message-ID: <20211108085918.GH2710@tucnak> (raw)
In-Reply-To: <499b9ae2-1365-a954-ed5e-35aede5d0def@suse.cz>
On Mon, Nov 08, 2021 at 09:45:39AM +0100, Martin Liška wrote:
> This fixes issue reported in the PR.
>
> Ready to be installed?
I'm not sure. liboffloadmic is copied from upstream, so the right
thing if we want to do anything at all (if we don't remove it, nothing
bad happens, the condition is never true anyway, whether removed away
in the source or removed by the compiler) would be to let Intel fix it in
their source and update from that.
But I have no idea where it even lives upstream.
Jakub
next prev parent reply other threads:[~2021-11-08 8:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:45 Martin Liška
2021-11-08 8:59 ` Jakub Jelinek [this message]
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 ` 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
-- strict thread matches above, loose matches on Subject: below --
2020-06-09 16:24 [PATCH] Remove dead code Richard Biener
2020-06-09 14:01 Richard Biener
2019-09-18 12:42 Richard Biener
2019-09-03 10:27 Richard Biener
2015-05-04 11:50 Dominik Vogt
2015-05-04 17:13 ` Jeff Law
2013-01-16 14:51 Richard Biener
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=20211108085918.GH2710@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=mliska@suse.cz \
--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).