search for: spec2006

Hi, What are the best options to compile Spec2006 with LLVM compilers to get the best performance numbers on x86? Has anybody compared LLVM Spec2006 numbers with GCC 4.5 base? reza -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100719/40cf38a5/attachment....

Hi Reza, -O4 is the highest level of LLVM optimization that I know of. But, I don't know if it has been tried on Spec2006. IIRC, Dan Gohman has run Spec. tests with LLVM, so he can provide more info. - fariborz On Jul 19, 2010, at 6:06 PM, Reza Yazdani wrote: > Hi, > > What are the best options to compile Spec2006 with LLVM compilers to > get the best performance numbers on x86? > > Has anybod...

On 07/20/10 18:03, Jim Grosbach wrote: > -O4 does give good additional performance compared to -O3 with llvm. The additional inlining opportunities and such add up quite a bit. The SPEC2006 runs I've done have all been within the framework of the llvm test suite, the LTO is run directly, rather than via an explicit -O4 option. The test-suite Makefiles themselves are probably the best place to look for the details of how that works if you're interested. SPEC2006 is hooked in vi...

...> I think the point here is that this is the default std for GCC but not > Clang, so you have to force clang to behave like GCC. For C++, you'll > have to force whatever default GCC has for it's C++ standard. right, but what option in clang++ forces it close to g++ for running spec2006 ? for clang it is apparent -std=gnu89 i understand that we have it configured already for test-suite but I also need to be able to run this standalone (outside of test-suite). > > Though, GCC 4.8 is getting very close to Clang's behaviour, so those > issues are bound to disappear...

On 16 August 2013 20:02, reed kotler <rkotler at mips.com> wrote: > -std=gnu89 is not valid for c++ > I think the point here is that this is the default std for GCC but not Clang, so you have to force clang to behave like GCC. For C++, you'll have to force whatever default GCC has for it's C++ standard. Though, GCC 4.8 is getting very close to Clang's behaviour, so

..."rw" which stands for protecting read and write accesses. In the > future, I will analyze how different flags affect ASan / SoftBoundCETS > / gcc-mpx / icc-mpx. > I will also use a set of microbenchmarks/benchmarks (e.g., RIPE) to > test the protection provided. > > > SPEC2006 is well know so it could be useful. Especially 483.xalancbmk > > Besides, maybe you could take something that is not strictly a benchmark. > > E.g. take pdfium_test (https://pdfium.googlesource.com/pdfium/) and feed > > several large pdf files to it. > > Thanks, I will repor...

Thank you, Adam. It passes all the benchmarks I have. Haicheng From: anemet at apple.com [mailto:anemet at apple.com] Sent: Wednesday, March 09, 2016 7:17 PM To: Haicheng Wu; Eric Christopher; Benjamin Kramer Cc: llvm-dev Subject: Re: Regression in SPEC2006/gcc caused by LoopLoadElimination I’ve committed the fix in r263058. Haicheng, Eric/Benjamin, can you guys please give it a test with your codebase. (You need to enable the pass with -mllvm -enable-loop-load-elim.) Thanks! Adam On Mar 7, 2016, at 11:05 PM, Adam Nemet <anemet at ap...

Hi Adam, I find LoopLoadElimination (r262250) causes SPEC2006/gcc generate wrong result (166.s) in AArch64 when running with *ref* data set. The error happens when I use either "-Ofast -flto -fuse-ld=gold" or "-O3 -fno-strict-aliasing". Please let me know if you need more information. Best, Haicheng -------------- next part ----...

...om here without further help from you. Adam > Thanks, > Adam > >> On Mar 7, 2016, at 8:33 AM, Haicheng Wu <haicheng at codeaurora.org <mailto:haicheng at codeaurora.org>> wrote: >> >> Hi Adam, >> >> I find LoopLoadElimination (r262250) causes SPEC2006/gcc generate wrong result (166.s) in AArch64 when running with *ref* data set. The error happens when I use either “-Ofast -flto -fuse-ld=gold” or “-O3 -fno-strict-aliasing”. Please let me know if you need more information. >> >> Best, >> >> Haicheng > -----------...

...IBM To: llvm-dev at lists.llvm.org Cc: junbuml at codeaurora.org, xinliangli at gmail.com Date: 11/02/2017 05:26 PM Subject: [RFC] Enable Partial Inliner by default Hello, I'd like to propose turning on the partial inliner (-enable-partial-inlining) by default. We've seen small gains on SPEC2006/2017 runtimes as well as lnt compile-times with a 2nd stage bootstrap of LLVM. We also saw positive gains on our internal workloads. ------------------------------------- Brief description of Partial Inlining ------------------------------------- A pass in opt that runs after the normal inlining...

...permail/llvmdev/2010-November/036013.html Although it doesn't seem to be a problem with the frontend, adding -std=gnu89, as suggested, fixed everything for me. H. ----- Original Message ----- From: reed kotler Sent: 08/16/13 01:26 AM To: LLVM Developers Mailing List Subject: [LLVMdev] running spec2006 with clang Has anyone been running this? Do you need to use one of the -std= or -ansi or whatever to set the language conformance level of clang to match some assumed gcc level? Tia. Reed _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llv...

Actually I am trying to run SPEC2006 through the Makefiles 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...

...9;-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/2013 02:26 PM, Izabela Maffra wrote: > 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="cl...

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...

...his locally. Should be able to make progress > from here without further help from you. > > Adam > > Thanks, > Adam > > On Mar 7, 2016, at 8:33 AM, Haicheng Wu <haicheng at codeaurora.org> wrote: > > Hi Adam, > > I find LoopLoadElimination (r262250) causes SPEC2006/gcc generate wrong > result (166.s) in AArch64 when running with *ref* data set. The error > happens when I use either “-Ofast -flto -fuse-ld=gold” or “-O3 > -fno-strict-aliasing”. Please let me know if you need more information. > > Best, > > Haicheng > > > >

...and write accesses. In the >>> future, I will analyze how different flags affect ASan / SoftBoundCETS >>> / gcc-mpx / icc-mpx. >>> I will also use a set of microbenchmarks/benchmarks (e.g., RIPE) to >>> test the protection provided. >>> >>> > SPEC2006 is well know so it could be useful. Especially 483.xalancbmk >>> > Besides, maybe you could take something that is not strictly a >>> benchmark. >>> > E.g. take pdfium_test (https://pdfium.googlesource.com/pdfium/) and >>> feed >>> > several lar...

...gcc.linked.rbc from the ...\Output folder that the LLVM test suite produces. Then I use this linked.rbc file to generate an executable file via the following commands: llc 403.gcc.linked.rbc -o 403.gcc.linked.s clang 403.gcc.linked.s -o 403.gcc.linked.exe This works with all the other programs in SPEC2006, but when I call clang for 403.gcc, I get errors due to missing symbols in cctype.h. I believe I must pass some compilation flags to clang, but I do not know which ones. The errors look like: /tmp/403-HRnVZ5.o: In function `check_format_info_main': 403.gcc.linked.rbc:(.text+0x2ec94): undefined...

...r me. > H. -std=gnu89 is not valid for c++ what did you use for that? tia. Reed >> ----- Original Message ----- >> >> From: reed kotler >> >> Sent: 08/16/13 01:26 AM >> >> To: LLVM Developers Mailing List >> >> Subject: [LLVMdev] running spec2006 with clang >> >> Has anyone been running this? >> >> Do you need to use one of the -std= or -ansi or whatever to set the >> language conformance level of clang to match some assumed gcc level? >> >> Tia. >> >> Reed >> >> >> &g...

Hi Sanjay, I observed some extra register spills when applying the reassociation pass on spec2006 benchmarks and I would like to listen to your advice. For example, function get_new_point_on_quad() of tria_boundary.cc in spec2006/dealII has a sequences of code like this . X=a+b . Y=X+c . Z=Y+d . There are many other instructions between these float adds. The reassociation p...

Has anyone been running this? Do you need to use one of the -std= or -ansi or whatever to set the language conformance level of clang to match some assumed gcc level? Tia. Reed