[8/9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken

Thomas Schwinge thomas@codesourcery.com
Mon Nov 11 09:15:00 GMT 2019


Hi!

On 2019-05-29T09:50:42-0600, Jeff Law <law@redhat.com> wrote:
> On 5/29/19 8:32 AM, Thomas Schwinge wrote:
>> On Thu, 9 May 2019 15:46:06 +0300, Ilya Verbin <iverbin@gmail.com> wrote:
>>> I have left Intel 3 years ago. If you have any questions regarding MIC
>>> offloading, you can reach me by iverbin@gmail.com
>> 
>> We're (a) looking for somebody to step up as a maintainer for that, and

That's still unresolved.

At the 2019 GNU Tools Cauldron, we discussed this topic in the OMP BoF,
and decided that despite its unmaintained status, we shall try to keep
GCC's Intel MIC (emulated) offloading support functional (at least until
any more complicated problems arise), because it might be useful for
Jakub once a year or so, for testing OMP changes.


>> (b) that person to get active, and take ownership of
>> <https://gcc.gnu.org/PR87833>, and review the proposed patch,
>> <http://mid.mail-archive.com/20190502213457.20953-1-hjl.tools@gmail.com>.
> My question would be where in the world is the -fno-pie stuff coming
> from.  It's also not clear where mkoffload is being called within c#5
> (presumably via the linker plugin) AFAICT we don't get the command line
> for that.  -v  or -Wl,-v probably would have helped.  It's difficult to
> know if HJ's patch is correct or not given the missing bits of information.
>
> But I'm willing to trust HJ here.  I'll ack the patch for the trunk.
> You or HJ can go ahead and install it.

I too have not made an attempt to really understand this problem and
solution.  See attached; as posted by H.J.,
<http://mid.mail-archive.com/20190502213457.20953-1-hjl.tools@gmail.com>,
I have now committed "[PR87833] x86: Put -fPIC and -shared the last to
create offload image" to trunk in r278041, gcc-9-branch in r278042,
gcc-8-branch in r278043.


> THe bigger question about the viability/usability of MIC is punted ;-)


Grüße
 Thomas


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-PR87833-x86-Put-fPIC-and-shared-the-last-to-cr.trunk.patch
Type: text/x-diff
Size: 2402 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20191111/679b1b26/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-PR87833-x86-Put-fPIC-and-shared-the-las.gcc-9-branch.patch
Type: text/x-diff
Size: 2428 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20191111/679b1b26/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-PR87833-x86-Put-fPIC-and-shared-the-las.gcc-8-branch.patch
Type: text/x-diff
Size: 2428 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20191111/679b1b26/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 658 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20191111/679b1b26/attachment.sig>


More information about the Gcc-patches mailing list