From: Thomas Schwinge <thomas@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>,
Tobias Burnus <tobias@codesourcery.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Hongtao Liu <hongtao.liu@intel.com>
Subject: Re: Remove support for Intel MIC offloading
Date: Fri, 4 Nov 2022 11:35:59 +0100 [thread overview]
Message-ID: <87fsezatww.fsf@dem-tschwing-1.ger.mentorg.com> (raw)
In-Reply-To: <Y2TprGZJ9irITc1R@tucnak>
Hi Jakub!
On 2022-11-04T11:30:04+0100, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Nov 04, 2022 at 10:54:02AM +0100, Thomas Schwinge wrote:
>> On 2022-10-20T22:56:57+0200, I wrote:
>> > 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:
>>
>> Taking your non-response as silent approval, I've now pushed to master
>
> I have responded in
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603988.html
That's correct, but later I sent this other email where I asked "Can you
please confirm: [...]", which had not gotten a response. (..., but I
convinced myself that my thinking was correct, so I now did proceed
understanding "non-response as silent approval".)
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
prev parent 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
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 [this message]
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=87fsezatww.fsf@dem-tschwing-1.ger.mentorg.com \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hongtao.liu@intel.com \
--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).