search for: calculatemhz

On 6 November 2012 22:34, Daniel Dunbar <daniel at zuster.org> wrote: > You are right, the failure on compile_time indicates that the test isn't > even building. As provided, the tests don't actually define the cpuida() or > calculateMHz() functions so that seems expected to me. I defined both functions as NOPs. I got what it was. The original makefile had a "-o lloops" on the compile command and I wrongfully copied it to the LDFLAGS, so it was generating the binary on the current dir, not on the Output dir, where it sh...

Hey Renato, You are right, the failure on compile_time indicates that the test isn't even building. As provided, the tests don't actually define the cpuida() or calculateMHz() functions so that seems expected to me. The compile failures end up getting buried in the logs, but they will either be in the test.log file in the top-level sandbox directory, or inside the <filename>.llvm.o.compile files in the Output directory for that test (i.e. SingleSource/Benchmarks...

Hi Daniel, I'm trying to add LivermoreLoops test to the benchmark suite (tar ball attached), but I'm getting the error below: --- Tested: 2 tests -- FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.compile_time (1 of 2) FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.execution_time (2 of 2) When I use the option to only run this test: --only-test