d954213667
The reason for the apparent slowness was that the "cpuid_tool" that was being called from run_tests.py is actually a shell script - a wrapper, installed by libtool. The script was heavy enough to cause substantial overhead. Just bypassing it (by using the real cpuid_tool binary) reduced "make test" running time from 4.1 to 0.7s on my machine. It is a bit hacky, though, so "make test-old" is retained, which uses the old invocation. |
||
---|---|---|
contrib/MSR Driver | ||
cpuid_tool | ||
debian | ||
libcpuid | ||
tests | ||
.gitignore | ||
AUTHORS | ||
ChangeLog | ||
configure.ac | ||
COPYING | ||
libcpuid.dsw | ||
libcpuid.pc.in | ||
libcpuid_vc9.sln | ||
libcpuid_vc71.sln | ||
Makefile.am | ||
NEWS | ||
README | ||
Readme.md |
libcpuid
libcpuid provides CPU identification for the x86 (and x86_64). For details about the programming API, please see the docs on the project's site (http://libcpuid.sourceforge.net/)
Configuring after checkout
Under linux, where you download the sources, there's no configure script to run. This is because it isn't a good practice to keep such scripts in a source control system. To create it, you need to run the following commands once, after you checkout the libcpuid sources from github:
1. run "libtoolize"
2. run "autoreconf --install"
You need to have autoconf
, automake
and libtool
installed.
After that you can run ./configure
and make
- this will build
the library.
make dist
will create a tarball (with "configure" inside) with the
sources.
Users
So far, I'm aware of the following projects which utilize libcpuid:
- CPU-X (https://github.com/X0rg/CPU-X)
- fre:ac (https://www.freac.org/)
- ucbench (http://anrieff.net/ucbench)
We'd love to hear from you if you are also using libcpuid and want your project listed above.