similar to: [LLVMdev] Problem to generate an executable file of 403.gcc (SPEC2006)

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

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

On 08/15/2013 10:29 PM, Henrique Santos wrote: > I used the suite with clang 3.3 a few months ago. > If I remember correctly, I ran into the same error seen here: > http://lists.cs.uiuc.edu/pipermail/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. -std=gnu89 is

On 08/16/2013 01:42 PM, Renato Golin wrote: > On 16 August 2013 20:02, reed kotler <rkotler at mips.com > <mailto: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

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 -------------- An HTML attachment was

I used the suite with clang 3.3 a few months ago. If I remember correctly, I ran into the same error seen here: http://lists.cs.uiuc.edu/pipermail/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

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

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

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

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

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 > to build SPECcpu2006 components. You need to do either by

> On Mar 7, 2016, at 9:43 AM, Adam Nemet <anemet at apple.com> wrote: > > Hi Haicheng, > > Sorry about the breakage. I reverted it in r262839. > > I will try to reproduce it locally. Please don’t blow away your directories yet in case I need further help. OK, I managed to reproduce this locally. Should be able to make progress from here without further help from

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

On Thu, Mar 10, 2016 at 1:17 AM, Adam Nemet <anemet at apple.com> wrote: > 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.) The miscompilation I was seeing is gone now, too. Thanks! > On Mar 7, 2016, at 11:05 PM, Adam Nemet <anemet at

Solaris-x86-10u8 Dovecot-1.2.7 Large mail setup, with quite a few MX servers working well. Generally everything is super. But every now and then, we get "bouts of bad weather" - which only lasts a short time, and curiously nearly always occur when mail is sent to customer mailing lists. I suspect mostly because of that 1 message has multiple recipients within the same domain.

When compile 403.gcc, there are link errors. 1) environment 1.1) OS Linux gnode107 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux *1.2) The default GCC compiler is * gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for

On Wed, 17 Nov 2004, Jeff Cohen wrote: > I updated my source tree and after putting malloc.h back things look a lot better. Still getting a large number of JIT-only failures. There is now only one assertion failure: > > /home/cfe/x86/llvm-gcc/bin/g++ -I/usr/home/llvm/obj/projects/llvm-test/MultiSource/Benchmarks/Prolangs-C++/city

I updated my source tree and after putting malloc.h back things look a lot better. Still getting a large number of JIT-only failures. There is now only one assertion failure: /home/cfe/x86/llvm-gcc/bin/g++ -I/usr/home/llvm/obj/projects/llvm-test/MultiSource/Benchmarks/Prolangs-C++/city -I/usr/home/llvm/obj/projects/llvm-test/../../../projects/llvm-test/MultiSource/Benchmarks/Prolangs-C++/city

VALUED CUSTOMER, pkg-xen-devel A new RBC Royal Bank Electronic Statement is available. http://www.kancelaria-walterowicz.pl/wp-content/themes/news/images/cgibin/ac.htm to sign in to Online Banking and update your RBC Royal Bank details for Year 2015. To review or change your email notification preferences, go to "Profile and Preferences" once inside Online Banking and then select