This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
libmvec requires x86?
- From: "Timothy Pearson" <kb9vqf at pearsoncomputing dot net>
- To: libc-alpha at sourceware dot org
- Date: Mon, 21 Dec 2015 12:58:18 -0600
- Subject: libmvec requires x86?
- Authentication-results: sourceware.org; auth=none
- Dkim-filter: OpenDKIM Filter v2.9.2 mail.pearsoncomputing.net 5424C640FEE
- Openpgp: id=2DAC594A8459AC61
- Reply-to: kb9vqf at pearsoncomputing dot net
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
Are there currently any plans to port libmvec to architectures other than
x86? I spent a rather fruitless day attempting to vectorize a floating
point calculation loop on POWER8 before realizing that libmvec is x86
only. We cannot use modern x86 hardware for internal security reasons,
and it came as something of a surprise that relatively advanced features
of glibc are only supported on x86, even though functionally equivalent
SIMD capabilities exist on other architectures (e,g, POWER8).
Would it be possible to get write access to
https://sourceware.org/glibc/wiki/libmvec so that I can at least add a
warning to not try to use libmvec on non-x86 architectures?
I'd be willing to try to port libmvec to POWER8 (or provide access to a VM
on the POWER8 hardware for any developer(s) willing to work on it), but I
don't really know where to start. What exactly is forcing libmvec to x86
only right now? Missing assembly functions or something deeper?
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlZ4S8oACgkQLaxZSoRZrGHj1QDfesRSwEGYwW0wba4u151nIRIt
NxKzmHi8ZadGMgDgsa951a5hDI+QQAdQUv+ezULdjteea6uRZmeYyg==
=9x1w
-----END PGP SIGNATURE-----