search for: speccpu2006

Using clang r107598 at -O1 to create reportable SPECINT 2006 results, I'm getting the output below, which is almost certainly due to a miscompilation. Known problem? Thanks, John Running (#3) 403.gcc ref base i386-m32-gcc42-nn default /home/regehr/z/specCPU2006/bin/specinvoke -d /home/regehr/z/specCPU2006/benchspec/CPU2006/403.gcc/run/run_base_ref_i386-m32-gcc42-nn.0000 -e speccmds.err -o speccmds.stdout -f speccmds.cmd -C 403.gcc: copy #0 non-zero return code (rc=1, signal=0) **************************************** Contents of c-typeck.err ********...

Hi If so, is it able to disable this check. All I need is just to get the BB coverage information Regards Muhui Alexander Potapenko <glider at google.com>于2018年9月5日 周三下午6:57写道： > This is a known problem in SPECCPU2006, see > https://github.com/google/sanitizers/wiki/AddressSanitizerFoundBugs > On Wed, Sep 5, 2018 at 7:36 AM Muhui Jiang via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > Hi > > > > I am using SanitizerCoverage feature supported by clang to get the &gt...

Hi I am using SanitizerCoverage feature supported by clang to get the basicblock coverage. my tested binaries are spec cpu2006. I compiled the binary with the option COPTIMIZE = -O0 -fsanitize=address -fsanitize-coverage=bb -flto -fno-strict-aliasing -std=gnu89 -gdwarf-3 After the compiling process is end. I run the 400.perlbench. with the command ASAN_OPTIONS=coverage=1 ./perlbench.

Hello, I'm trying to generate bitcode files from the SPEC CPU2006 benchmark suites. First I installed the benchmarks into ~/llvm/projects/test-suite/External/speccpu2006 and then I tried ~/mysandbox/bin/lnt runtest nt --sandbox=sandbox --cc=/Users/asd/llvm/Release/bin/clang --test-suite=/Users/asd/llvm/projects/test-suite --test-externals=/Users/asd/llvm/projects/test-suite/External -j 4 --only-test=External/SPEC --enable-jit It looks like all but two tests did r...

...> > If so, is it able to disable this check. All I need is just to get the > BB coverage information > > > > Regards > > Muhui > > > > Alexander Potapenko <glider at google.com>于2018年9月5日 周三下午6:57写道： > >> > >> This is a known problem in SPECCPU2006, see > >> https://github.com/google/sanitizers/wiki/AddressSanitizerFoundBugs > >> On Wed, Sep 5, 2018 at 7:36 AM Muhui Jiang via llvm-dev > >> <llvm-dev at lists.llvm.org> wrote: > >> > > >> > Hi > >> > > >> > I am us...

...or spec95 benchmark sources... no, not found in /home/vadve/shared/ben chmarks/spec95/benchspec checking for spec2000 benchmark sources... no, not found in /home/vadve/shared/b enchmarks/speccpu2000/benchspec checking for spec2006 benchmark sources... no, not found in /home/vadve/shared/b enchmarks/speccpu2006/benchspec checking for povray benchmark sources... no, not found in /home/vadve/shared/ben chmarks/povray31 checking for namd benchmark sources... no, not found in /home/vadve/shared/bench marks/spec_namd checking for sweep3d benchmark sources... no, not found in /home/vadve/shared/be nchmarks/swee...

...gt; > chmarks/spec95/benchspec > > checking for spec2000 benchmark sources... no, not found in /home/ > > vadve/shared/b > > enchmarks/speccpu2000/benchspec > > checking for spec2006 benchmark sources... no, not found in /home/ > > vadve/shared/b > > enchmarks/speccpu2006/benchspec > > checking for povray benchmark sources... no, not found in /home/ > > vadve/shared/ben > > chmarks/povray31 > > checking for namd benchmark sources... no, not found in /home/vadve/ > > shared/bench > > marks/spec_namd > > checking for sweep3d b...

...s of QAV is 'metadata' and should not alias with any actual accesses in the program. I've compiled the same code with GCC and it was able to hoist most of the address calculations out as expected. GCC was able to hoist address calculations for Q also. This is an actual piece of code in SPECCPU2006 437.leslie3d and the loop I analyzed is in line 1630 of file tml.f. 437.leslie3d suffers horrible performance problems because of this and similar problems. Is there anyway to enable this optimization? Is there a way to flag in the IR that a particular locations is array dimension meta data? Than...

...n /home/ > vadve/shared/ben > chmarks/spec95/benchspec > checking for spec2000 benchmark sources... no, not found in /home/ > vadve/shared/b > enchmarks/speccpu2000/benchspec > checking for spec2006 benchmark sources... no, not found in /home/ > vadve/shared/b > enchmarks/speccpu2006/benchspec > checking for povray benchmark sources... no, not found in /home/ > vadve/shared/ben > chmarks/povray31 > checking for namd benchmark sources... no, not found in /home/vadve/ > shared/bench > marks/spec_namd > checking for sweep3d benchmark sources... no, not found...

...(no platform-specific optimizations have been implemented yet) Given this set of limitations, the current status is - Working C/C++ compiler * Passes internal testsuite and projects/test-suite with no failures * Passes a full bootstrap with identical stage2/stage3 results * Builds and runs SPECcpu2006 benchmarks successfully * Passes the ABI compatibility test suite against GCC 4.8 - Working integrated assembler * Passes both testsuites with integrated assembler forced on - Working assembler parser * Passes both testsuites when using clang assembler instead of system assembler - Working MC...

I can't really tell what is happening based on this output, but 'make' is not the right way to build SPECcpu2006 components. You need to do either by using the supplied 'runspec' command with '-build' action directive or to issue the 'specmake' (which is a make adjusted by spec.org) on the build component folder. I can build 433.milc on PPC64 with clang without any issue. On 02/18/20...

...benchspec >> > checking for spec2000 benchmark sources... no, not found in /home/ >> > vadve/shared/b >> > enchmarks/speccpu2000/benchspec >> > checking for spec2006 benchmark sources... no, not found in /home/ >> > vadve/shared/b >> > enchmarks/speccpu2006/benchspec >> > checking for povray benchmark sources... no, not found in /home/ >> > vadve/shared/ben >> > chmarks/povray31 >> > checking for namd benchmark sources... no, not found in /home/vadve/ >> > shared/bench >> > marks/spec_namd >>...

...akefiles provided with LLVM Test Suite, so I think it should work properly... On 18 February 2013 15:49, Adhemerval Zanella <azanella at linux.vnet.ibm.com>wrote: > I can't really tell what is happening based on this output, but 'make' is > not the right way > to build SPECcpu2006 components. You need to do either by using the > supplied 'runspec' > command with '-build' action directive or to issue the 'specmake' (which > is a > make adjusted by spec.org) on the build component folder. > > I can build 433.milc on PPC64 with clang wi...

...a' and should not alias with any > actual accesses in the program. I've compiled the same code with GCC > and it was able to hoist most of the address calculations out as > expected. GCC was able to hoist address calculations for Q also. > > This is an actual piece of code in SPECCPU2006 437.leslie3d and the > loop I analyzed is in line 1630 of file tml.f. 437.leslie3d suffers > horrible performance problems because of this and similar problems. > > Is there anyway to enable this optimization? Is there a way to flag in > the IR that a particular locations is array di...

...ounters + Implements efficient event counting [Ball94] to reduce instrumentation overheads + Context sensitive counters if no 64-bitoverflow (i.e. supports path profiling across recursion) + Optimizations for use cases with very large number of executed paths + Used to analyse C/C++ benchmarks from SPECCPU2006 Proposed Integration : + Support library code added to compiler-rt + llvm/Analysis gets PathEncoding, PathDecoding and PathProfileInfo module passes + llvm/Transforms/Instrumentation gets PathProfileInstrumentation module pass + PathProfileInfo offers const only public methods to query info Open...

Dear LLVMers, I am having trouble to run SPEC2006. I have checked in my log file that the spec root has been correctly found with ./configure, but when I try: make TEST=simple in the External folder I get the following error: make -C /home/izabela/svn_llvm/llvm/projects/test-suite/tools all \ ORIGINAL_CC="clang" \ ORIGINAL_CXX="clang" make[1]: Entering directory

...is the document written by you https://fosdem.org/2018/schedule/event/crosscompile/attachments/slides/2107/export/events/attachments/crosscompile/slides/2107/How_to_cross_compile_with_LLVM_based_tools.pdf I follow it to try to use the clang to do cross compilation. Actually, my target binaries is SPECCPU2006 and autotools based binaries. However, I failed on the first step. I write a hello world as test.c. I refer to your document and download the newest version of arm toolchain. I use the following command to try to compile the code to binary. sudo /home/jmh/Downloads/llvm/build/bin/clang --sysroo...

...I am having trouble getting the test suite set up with my download of SPEC2006. I downloaded and installed llvm-gcc, checked out a copy of test-suite in llvm-2.8/projects, and then configured and made llvm: ./configure --enable-debug-runtime --disable-optimized --enable-spec2006=/home/jamiemmt/speccpu2006 --with-externals=/home/jamiemmt make The configure script found the SPEC source code. Then, within projects/test-suite/External/SPEC. I ran make and got: make[1]: Entering directory `/home/jamiemmt/llvm-2.8/projects/test-suite/SingleSource' make[2]: Entering directory `/home/jamiemmt/llvm-2...

...gt; > chmarks/spec95/benchspec > > checking for spec2000 benchmark sources... no, not found in /home/ > > vadve/shared/b > > enchmarks/speccpu2000/benchspec > > checking for spec2006 benchmark sources... no, not found in /home/ > > vadve/shared/b > > enchmarks/speccpu2006/benchspec > > checking for povray benchmark sources... no, not found in /home/ > > vadve/shared/ben > > chmarks/povray31 > > checking for namd benchmark sources... no, not found in /home/vadve/ > > shared/bench > > marks/spec_namd > > checking for sweep3d b...

> I'd like to propose the addition of a new SystemZ backend to the LLVM and > Clang code base. We're interested in this for the same reason we've been > interested in the PowerPC back-end recently: to enable packages in upcoming > enterprise Linux distributions that need LLVM support (e.g. 3D desktop > support via llvmpipe). Cool! > - focus on feature completeness