From: Aaron Webster <awebster@falsecolour.com>
To: libffi-discuss@sourceware.org
Subject: libffi intel icc and src/x86/ffi64.c
Date: Tue, 03 Apr 2012 13:31:00 -0000 [thread overview]
Message-ID: <20120403133135.GA21331@cshpc.rrze.uni-erlangen.de> (raw)
I've seen some things on the internet about people trying to build libffi
with intel icc, which doesn't define __int128_t.
I've found that you can just use
long long sse[MAX_SSE_REGS];
instead of __int128_t in src/x86/ffi64.c, and everything will compile fine.
I think the real intel type is something like __m128, but I'm not 100%
sure.
--
Aaron Webster
next reply other threads:[~2012-04-03 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 13:31 Aaron Webster [this message]
2012-04-06 12:48 ` Anthony Green
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=20120403133135.GA21331@cshpc.rrze.uni-erlangen.de \
--to=awebster@falsecolour.com \
--cc=libffi-discuss@sourceware.org \
/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).