From: Michael Shell <list1@michaelshell.org>
To: libffi-discuss@sourceware.org
Cc: green@moxielogic.com
Subject: libffi misidentifies certain older Intel CPU capabilites
Date: Sat, 26 May 2018 18:42:00 -0000 [thread overview]
Message-ID: <20180526144420.d153aa01884dae20cbedefc4@michaelshell.org> (raw)
Anthony and other libffi developers/users,
Over at the Linux From Scratch site, we've been seeing users get bitten
by a bug in libffi where it thinks certain Intel processors have
capabilites they actually don't which results in Illegal Instruction
errors. Specifically, gcc, or at least the most recent version of it,
is employing the vmovq instruction on CPUs that don't support it,
e.g., Celeron G530 and G640T:
http://lists.linuxfromscratch.org/pipermail/lfs-support/2018-May/051993.html
http://lists.linuxfromscratch.org/pipermail/lfs-support/2018-May/052029.html
Solved here:
http://lists.linuxfromscratch.org/pipermail/lfs-support/2018-May/052008.html
So, libffi needs to disable support for avx and aes instructions on
Intel CPUs that don't support them. Just thought I'd send you a heads
up on this issue.
Cheers and thanks,
Mike Shell
reply other threads:[~2018-05-26 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180526144420.d153aa01884dae20cbedefc4@michaelshell.org \
--to=list1@michaelshell.org \
--cc=green@moxielogic.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).