From: Anthony Green <green@moxielogic.com>
To: Andrew Haley <aph@redhat.com>
Cc: pinskia@gmail.com,
"libffi-discuss\@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: Xeon Phi
Date: Tue, 14 Oct 2014 09:52:00 -0000 [thread overview]
Message-ID: <87egubf06x.fsf@moxielogic.com> (raw)
In-Reply-To: <543CEA22.9020302@redhat.com> (Andrew Haley's message of "Tue, 14 Oct 2014 10:17:22 +0100")
Andrew Haley <aph@redhat.com> writes:
> On 14/10/14 10:16, pinskia@gmail.com wrote:
>
>>
>>> On Oct 14, 2014, at 2:14 AM, Andrew Haley <aph@redhat.com> wrote:
>>>
>>> What's the status of Xeon Phi support? There seem to be some packages on the
>>> Interweb, but I don't see anything in libffi git.
>>
>> Xeon phi is just x86_64 linux.
>
> No it's not. There is a completely different FPU and a different ABI.
Yes, there's no SSE instructions, and more...
Somebody needs to find the relevant changes in here and submit them:
https://github.com/bpartridge/xeon_phi_ctypes/tree/master/libffi
AG
next prev parent reply other threads:[~2014-10-14 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:14 Andrew Haley
2014-10-14 9:16 ` pinskia
2014-10-14 9:17 ` Andrew Haley
2014-10-14 9:52 ` Anthony Green [this message]
2014-10-14 10:08 ` Jakub Jelinek
2014-10-14 10:23 ` Andrew Haley
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=87egubf06x.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=aph@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=pinskia@gmail.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).