| Age | Commit message (Collapse) | Author |
|---|
|
Use just the symbolic name "hardinfo", allowing for icon packs to
provide alternative icons.
Fixes #227
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
The idea here is to make adding/removing benchmark tests easier by
having benchmark.c be the framework and all the functioned needed
for individual benchmarks live in benches.c.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Benchmark results store actual number of threads used by benchmark
when it was run. Previously, results assumed all available threads
were used.
Examples:
* CPU Fib only uses one
* FPU FFT uses 4, 2, or 1
* N-Queens uses 10, 5, 2, or 1
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Other minor tweaks.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
In the future, won't have to rely on a translated string.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
For the GPU Drawing benchmark at least, it should give
some idea of the graphics capabilities of the machine.
This is the only data hardinfo currently has about that.
Maybe in the future, more advanced GPU information could
be given.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* cpu_config string is translated as loaded
* if board or cpu_desc is missing, it is left null, stored empty, and
translated to (Unknown) only when displayed.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* hide bench/name and result
* expand note for old results
The old version is kept because it is useful for future
development.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Old versions of hardinfo used current frequency instead of max
frequency. If the cpu id string had a clock rate in it, and it is
significantly more than thre reported frequency in the benchmark
result, use that.
This feature exists in an earlier commit but it was broken.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* More information can be saved in benchmark.conf, while still being
compatible with older versions.
* Selecting a result give additional information about the result
and the machine the produced it.
|
|
|
|
|
|
|
|
|
|
|
|
gcc was (correctly) assuming that benchmark_parallel_for() returned
an integer, which was being to a double and messing up results. Added
the missing prototype.
Also, populate bench_results array with sane values on module init.
Some other minor cleanups in benchmark code.
|
|
|
|
|
