From: Thomas Schwinge <thomas@codesourcery.com>
To: Ilya Verbin <iverbin@gmail.com>, Jakub Jelinek <jakub@redhat.com>,
<gcc@gcc.gnu.org>
Subject: Re: [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken (was: GCC 9.0.1 Status Report (2019-04-25))
Date: Tue, 30 Apr 2019 10:48:00 -0000 [thread overview]
Message-ID: <87h8afixb9.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <87r29jg4o2.fsf@euler.schwinge.homeip.net>
Hi!
Email to <ilya.verbin@intel.com> apparently is no longer gets delivered.
Is there anyone else from Intel who'd take over maintenance?
Grüße
Thomas
On Tue, 30 Apr 2019 12:37:17 +0200, I wrote:
> Hi!
>
> On Thu, 25 Apr 2019 20:38:21 +0200, Jakub Jelinek <jakub@redhat.com> wrote:
> > branches/gcc-9-branch has
> > been created; GCC 9.1-rc1 will be built and announced likely tomorrow.
>
> Yay! \o/
>
>
> I just again want to point to <https://gcc.gnu.org/PR87833> '[9/10
> Regression] Intel MIC (emulated) offloading: "relocation [...] can not be
> used when making a shared object; recompile with -fPIC"'.
>
> This not being fixed means that Intel MIC (emulated) offloading will be
> broken in the upcoming GCC 9 release. As in the past several months
> apparently nobody but me has run into this (or didn't bother to report
> it), I thus again wonder whether anyone but me is still testing Intel MIC
> (emulated) offloading, and/or there's no interest anymore in keeping this
> functional?
>
> My WIP patch/work around still works (but is still as WIP as it was
> before).
>
>
> Grüße
> Thomas
next prev parent reply other threads:[~2019-04-30 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 18:38 GCC 9.0.1 Status Report (2019-04-25) Jakub Jelinek
2019-04-25 21:32 ` Jonathan Wakely
2019-04-30 10:37 ` [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken (was: GCC 9.0.1 Status Report (2019-04-25)) Thomas Schwinge
2019-04-30 10:48 ` Thomas Schwinge [this message]
2019-04-30 10:57 ` Jakub Jelinek
2019-04-30 11:02 ` Thomas Schwinge
2019-04-30 11:31 ` Jakub Jelinek
2019-05-07 8:03 ` Hongtao Liu
2019-05-09 12:46 ` Ilya Verbin
2019-05-29 14:32 ` [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken Thomas Schwinge
2019-05-29 15:50 ` Jeff Law
2019-11-11 9:13 ` [8/9/10 " 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=87h8afixb9.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=iverbin@gmail.com \
--cc=jakub@redhat.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).