search for: generatereport

...ors in the 'test' rule were dutifully ignored (I think). So far so good. But I had some errors on the 'report' rule, which I wasn't expecting. make: *** [report.simple.raw.out] Error 2 make: Target `report' not remade because of errors. /home/rengolin/devel/llvm/test-suite/GenerateReport.pl -csv /home/rengolin/devel/llvm/test-suite/TEST.simple.report < report.simple.raw.out > report.simple.csv /bin/sh: 1: cannot open report.simple.raw.out: No such file make: *** [report.simple.csv] Error 2 And that stops the process. $ make report Didn't work, but I guess that's d...

On 27 October 2012 01:17, Daniel Dunbar <daniel at zuster.org> wrote: > Can you include the output of build-tools.log in that directory, please? Ah, yes! Relative path on clang++ binary. I understand why it works to get the version but not here (different paths). Would be good to have some warning (or even an error) if one passes a relative path. Or, possibly, save the current path and

...metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data collection and reporting mechanism in llvm has mostly shifted to LNT these days. In any case it should be easy to use “lit -o result.json” and process the resulting json file in your favorite scripting language to generate arbitrary...

...h/src/llvm-test-2.1/SingleSource/UnitTests' make[2]: *** [UnitTests/.maketest] Error 2 make[2]: Leaving directory `/home/mth/src/llvm-test-2.1/SingleSource' make[1]: *** [SingleSource/.maketest] Error 2 make[1]: Leaving directory `/home/mth/src/llvm-test-2.1' /home/mth/src/llvm-test-2.1/GenerateReport.pl /home/mth/src/llvm-test-2.1/TEST.nightly.report < report.nightly.raw.out > report.nightly.txt Program | GCCAS Bytecode LLC compile LLC-BETA compile JIT codegen | GCC CBE LLC LLC-BETA JIT | GCC/CBE GCC/LLC GCC/LLC-BETA LLC/LLC-BETA mth at starbug-3:~/src/llvm-test-2.1> Since several...

...metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data collection and reporting mechanism in llvm has mostly shifted to LNT these days. In any case it should be easy to use “lit -o result.json” and process the resulting json file in your favorite scripting language to generate arbitrary...

...izes for different segments, compiletime, linktime, executable hash, > execution time. I designed it be easily extensible with further metrics. > Not all of these metrics are understood by LNT yet so they may get lost > after submission to an LNT database. > > > > We do not use GenerateReport.pl and friends in the cmake/lit version > anymore, as the main data collection and reporting mechanism in llvm has > mostly shifted to LNT these days. In any case it should be easy to use “lit > -o result.json” and process the resulting json file in your favorite > scripting language to...

...I get this error with Rserve: eval failedeval failed, request status: R parser: syntax erroreval failed, request status: R parser: input incompleteorg.rosuda.REngine.Rserve.RserveException: eval failed at org.rosuda.REngine.Rserve.RConnection.eval(RConnection.java:233) at se.ucr.qrep.RGenerator.generateReport(RGenerator.java:45) Anyone know what it could mean? -- View this message in context: http://r.789695.n4.nabble.com/Error-with-Rserv-tp3074458p3074458.html Sent from the R help mailing list archive at Nabble.com.

...re dutifully ignored (I > think). So far so good. > > But I had some errors on the 'report' rule, which I wasn't expecting. > > make: *** [report.simple.raw.out] Error 2 > make: Target `report' not remade because of errors. > /home/rengolin/devel/llvm/test-suite/GenerateReport.pl -csv > /home/rengolin/devel/llvm/test-suite/TEST.simple.report < > report.simple.raw.out > report.simple.csv > /bin/sh: 1: cannot open report.simple.raw.out: No such file > make: *** [report.simple.csv] Error 2 > > And that stops the process. > > $ make report >...

...already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. > > We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data collection and reporting mechanism in llvm has mostly shifted to LNT these days. In any case it should be easy to use “lit -o result.json” and process the resulting json file in your favorite scripting language to generate arbitrary...

Rick Sullivan <ricks at carbondesignsystems.com> writes: [snip] > The problem is this. For some simulations, the LLVM shared library > seems to take a segfault on exit. It runs correctly, but when the > simulator finishes, it crashes on exit. [snip] > > Does anybody have any ideas as to why this might be happening? Can you run the application under gdb and obtain a

..., but it doesn't supply much information: 0: /o/release/SoCD/mainline/PRODUCT/Linux/bin/Linux//release/socdesigner(_ZN12CrashHandler12GetBacktraceEPc+0x2b) [0x8209adb] CrashHandler::GetBacktrace(char*) 1: /o/release/SoCD/mainline/PRODUCT/Linux/bin/Linux//release/socdesigner(_ZN12CrashHandler14GenerateReportEv+0x204) [0x820a434] CrashHandler::GenerateReport() 2: /o/release/SoCD/mainline/PRODUCT/Linux/bin/Linux//release/socdesigner(_ZN12CrashHandler21DoAllReportGenerationEv+0x1c) [0x820a51c] CrashHandler::DoAllReportGeneration() 3: /o/release/SoCD/mainline/PRODUCT/Linux/bin/Linux//release/socdesigner(...

We're using the LLVM 3.3 AArch64 disassembler in the following way. We have built LLVM 3.3 on Linux as a shared library; and have a main program that dynamically loads shared objects (.so libraries). The program is a simulator (though that shouldn't be relevant to this question), and the shared objects it loads are electronic components that participate in the simulation. If the electronic

...metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data collection and reporting mechanism in llvm has mostly shifted to LNT these days. In any case it should be easy to use “lit -o result.json” and process the resulting json file in your favorite scripting language to generate arbitrary...

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

Hi all, As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT. One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we can run LIT and get report which is not equal with report (simple) got with make. Cmake test-suite version has no features to run custom