similar to: [LLVMdev] specint 2000 with llvm as test-suite

Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] specint 2000 with llvm as test-suite"

2011 Jun 29
0
[LLVMdev] specint2000 as external tests
My source directory wasn't correct but now I have a correct test directory structure. $ls -1 ~/tmp/speccpu2000/benchspec/CINT2000/164.gzip/ data docs exe result run Spec src version I reconfigured the llvm with ../configure --prefix=/home/dskhudia/tmp/llvm-install --with-llvmgccdir=/home/dskhudia/tmp/llvm-install --with-externals=/home/dskhudia/tmp Now I can execute the make -C 164.gzip but
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
Hello, Some problems were solved, new ones arised... Getting closer though... The fixes for the previous problems are at the bottom of this email, bug reports will be submitted when all problems are solved. +++ New/remaining problems +++ Currently, 9/26 benchmarks compile and run succesfully. One (fma3d) still has a f95 related problem (see below). The other 16 are divided into two groups:
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Fri, 1 Sep 2006, Kenneth Hoste wrote: > Some problems were solved, new ones arised... Getting closer though... > The fixes for the previous problems are at the bottom of this email, > bug reports will be submitted when all problems are solved. Kenneth, In general, I am more than happy to help people on this list. It is good for the community and I enjoy helping people be successful
2011 Jun 29
3
[LLVMdev] specint2000 as external tests
Hi Duncan, Do you have sources also in the $LLVM_SRC_ROOT/projects/test-suite/External/SPEC/CINT2000/164.gzip? The following is content of above directory in my case. I have copied the CINT2000 sources in this directory manually. $ls -1 $LLVM_SRC_ROOT/projects/test-suite/External/SPEC/CINT2000/164.gzip 164.gzip.reference_output 164.gzip.reference_output.small compile_info compile_parms
2007 Aug 30
0
[LLVMdev] Pre-2.1 Status
In preparation for the release, I've compared the llvm-test results for current SVN and the 2.0 release to see how many regressions we have currently. Things are looking really good! Darwin/x86: 2 llvm-test regressions MultiSource/Benchmarks/MiBench/office-ispell/office-ispell (CBE) MultiSource/Benchmarks/Prolangs-C/cdecl/cdecl (CBE) Linux/x86: 5 llvm-test failures
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On 01 Sep 2006, at 10:05, Kenneth Hoste wrote: > >> >>> Also, it is possible to tell make only to compile benchmark X? How >>> can I >>> enforce this? >> >> Go into the directory for that benchmark, then run 'make' or >> whatever. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective
2005 Nov 07
0
[LLVMdev] LLVM 1.6 Release Branch
Everything builds fine on sparc. The configure script needs to be fixed though (see previous email). Sparc testing results: make check: # of expected passes 1189 # of expected failures 34 Regressions Single Source: None New Failures Single Source (new tests): 2005-05-12-Int64ToFP: llc,jit Regressions MultiSource: Applications/d/make_dparser: llc, cbe, jit
2005 May 13
2
[LLVMdev] Current Regressions
Chris Lattner wrote: > On Thu, 12 May 2005, John Criswell wrote: > >> Here is a more complete list of regressions for the platforms listed >> below. Some of the regressions from the previous list I emailed a few >> days ago have been fixed or were false positives. Thanks to all >> who've helped fix things. >> >> We would like to try to get as many
2008 Mar 01
1
[LLVMdev] Instruction Scheduling
Hi, guys, I am comparing the performance of the default scheduler (seems to be the one that minimizes register pressure) with no scheduler (-pre-RA-sched=none), and I got these numbers. The ratio is low_reg_pressure/none, that is, the lower the number, the better the performance with low register pressure: CFP2000/177.mesa/177.mesa 1.00 CFP2000/179.art/179.art
2010 Feb 15
0
[LLVMdev] Measurements of the new inlinehint attribute
Friday I enabled the inlinehint function attribute in the inliner. It mostly affects the performance of -Os compiled code. I have made some measurements on the SPEC test suite to show what it means. I made three runs of then nightly tests. The baseline represents -Os with no inlinehint: make TEST=nightly OPTFLAGS=-Os EXTRA_LOPT_OPTIONS=-inlinehint-threshold=0
2011 Apr 30
2
[LLVMdev] Greedy register allocation
Perhaps you noticed that LLVM gained a new optimizing register allocator yesterday (r130568). Linear scan is going away, and RAGreedy is the new default for optimizing builds. Hopefully, you noticed because your binaries were suddenly 2% smaller and 10% faster*. Some noticed because LLVM started crashing or miscompiling their code. Greedy replaces a fairly big chunk of the code generator, so
2005 Nov 07
0
[LLVMdev] LLVM 1.6 Release Branch
>> Everything builds fine on sparc. The configure script needs to be fixed >> though (see previous email). > > I'm not getting the error with the configure script (on Kain, anyway). I've > tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my > $PATH. I get the error with and without the --with-f2c option. I never used the NAG Fotran
2005 Nov 07
4
[LLVMdev] LLVM 1.6 Release Branch
Tanya Lattner wrote: > > Everything builds fine on sparc. The configure script needs to be fixed > though (see previous email). I'm not getting the error with the configure script (on Kain, anyway). I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my $PATH. Can you verify that the configure script works for you without the --with-f2c option?
2010 Jul 23
3
[LLVMdev] some undefined behaviors in llvm/clang
Hi folks, Below is a short list of integer undefined behaviors executed by Clang when compiling the LLVM test suite. They seem pretty self explanatory, but let me know if not, if you cannot reproduce any of them, or if it would be better for me to file bugzillas on them. This is on x64 Linux, using r108984. Thanks, John --------------------------------- CLANG UNDEFINED at
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On 31 Aug 2006, at 23:46, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> Bummer. I think I'll contact the NAG support for more info on >> this. Can you >> show me the content of your Makefile.nagfortran? > > It is identical to yours. > >> Also, it is possible to tell make only to compile benchmark X? How >> can I >>
2005 May 13
0
[LLVMdev] Current Regressions
On Fri, 13 May 2005, John Criswell wrote: > These following regression tests are failing (didn't mention these before > because they're easy to spot in nightly tester emails): > > FAIL: /Users/criswell/llvm/test/Regression/CodeGen/Generic/print-arith-fp.ll: > FAIL: > /Users/criswell/llvm/test/Regression/CodeGen/X86/fast-cc-pass-in-regs.ll: > FAIL:
2011 Jul 07
0
[LLVMdev] llvm-gcc cross compiling for ARM
Here is how I do it on x86-64 machine running Ubuntu-11.04: 1. install flex and bison 2. download arm-2011.03 from www.codesourcery.com and add to path (setenv PATH ${PATH}:/home/dskhudia/projects/arm-2011.03/bin) 3. mkdir llvm-gcc-obj; cd llvm-gcc-obj 4. ../llvm-gcc-4.2-2.9.source/configure --target=arm-none-linux-gnueabi --program-prefix=llvm-
2011 Jul 08
1
[LLVMdev] as: unrecognized option '-meabi=4'
Hi In my install directory under bin , I had llvm-c++,llvm-g++,llvm-gconv I tested one sample program #llvm-c++ addu.c -o addu-arm as: unrecognized option '-meabi=4' How do i solve this issue Thanks Yuvi R On Fri, Jul 8, 2011 at 9:21 AM, raj raja <yuvaraj.addu at gmail.com> wrote: > Thanks for your reply > > I got error > > */bin/sh: build/genmodes: not
2011 Jul 08
0
[LLVMdev] as: unrecognized option '-meabi=4'
Hi Thanks your info On 7/8/11, James Molloy <james.molloy at arm.com> wrote: > Hi, > > > > It sounds like you're using an incorrect version of binutils (one that > targets x86 instead of ARM, for example). > > > > You require an ARM-targetting assembler and linker. > > > > James > > > > From: llvmdev-bounces at cs.uiuc.edu
2012 Apr 14
1
[LLVMdev] Running test suite with LNT failed
> >  But I got the error message below, > > > > --- > > 2012-04-12 02:39:48: executing test modules > > 2012-04-12 02:39:49: loading nightly test data... > > nt.py:737: fatal error: nightly test failed, no report generated > > --- > > > >  Any idea on how I can figure out what the fatal error is? Thanks! > > Inside the sandbox there will