similar to: [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode"

2006 Aug 30
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Wed, 30 Aug 2006, Kenneth Hoste wrote: > I've been trying (on and off) to compile the _full_ SPEC CPU2000 benchmark > suite to LLVM bytecode. The biggest problem > I'm facing is the Fortran benchmarks, for which some partial support is > already available it seems (using f2c). ok. > Unfortunately the f2c compiler only allows the translation of Fortran-77 >
2006 Aug 30
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
Hi Chris, > > I use NAG with llvm-gcc4. What sort of errors do you get? Did you > configure llvm-test with the appropriate flags to find it? > Yes, I did. llvm-test is configured as follows: (in /work/LLVM/1.8/ llvm/project/llvm-test): ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec -- without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/work/
2006 Aug 30
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Wed, 30 Aug 2006, Kenneth Hoste wrote: >> I use NAG with llvm-gcc4. What sort of errors do you get? Did you >> configure llvm-test with the appropriate flags to find it? > Yes, I did. llvm-test is configured as follows: (in /work/LLVM/1.8/ > llvm/project/llvm-test): > ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec -- > without-f2c
2006 Aug 31
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 > enforce this? Go into the directory for that benchmark, then run 'make' or whatever. -Chris --
2006 Aug 31
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On 31 Aug 2006, at 19:13, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: > >> When I adjust the settings in Makefile.nagfortran as follows, I'm >> able to get bytecode file for lucas, galgel and facerec, but make >> still quits with an error (after generating >> bytecode files for 7 (out of 26) benchmarks. >> >> Also, the file
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 >>
2006 Aug 31
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On 30 Aug 2006, at 23:04, Chris Lattner wrote: > On Wed, 30 Aug 2006, Kenneth Hoste wrote: >>> I use NAG with llvm-gcc4. What sort of errors do you get? Did >>> you configure llvm-test with the appropriate flags to find it? >> Yes, I did. llvm-test is configured as follows: (in /work/LLVM/ >> 1.8/ llvm/project/llvm-test): >> ./configure
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
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 Aug 31
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> $ grep F95 .../projects/llvm-test/Makefile.config > > -bash-3.00$ grep F95 projects/llvm-test/Makefile.config > # F95: Enable LLVM to run Fortran benchmarks without a Fortran front-end > USE_F95=1 > F95_DIR := > F95 := /work/NAG_f95/bin/f95 > F95_INC := /work/NAG_f95/lib > F95_LIB := /work/NAG_f95/lib > > Looks
2006 Aug 31
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On 31 Aug 2006, at 07:58, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >>> $ grep F95 .../projects/llvm-test/Makefile.config >> >> -bash-3.00$ grep F95 projects/llvm-test/Makefile.config >> # F95: Enable LLVM to run Fortran benchmarks without a Fortran >> front-end >> USE_F95=1 >> F95_DIR := >> F95 :=
2006 Nov 25
2
[LLVMdev] f95 problem with SPEC2K
Anyone know what to do about this: make[4]: Leaving directory `/proj/llvm/llvm-test-1/External/SPEC/CFP2000/173.applu' make[4]: Entering directory `/proj/llvm/llvm-test-1/External/SPEC/CFP2000/178.galgel' /usr/bin/f95 -w -S -O2 /opt/spec/CPU2000v1.3.1/benchspec//CFP2000/178.galgel/src/modules.f90 -o modules.c -fixed -kind=byte -dcfuns -dusty f95: unrecognized option '-kind=byte'
2006 Aug 09
2
[LLVMdev] compiling SPEC suite using f95
Hello, I'm trying to compile to SPEC CPU2000 suite to LLVM bytecode, using the llvm-test harness. I have tried this using: - both the 1.7 and 1.8 releases, without succes (and running into the same problems in both releases) - both the gcc3 and gcc4 frontends I'm working on Linux/x86. LLVM is configured using: ./configure --prefix=/path/to/bin/dir and compiled using gmake; gmake
2006 Aug 31
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> It doesn't to me. If you set F95_DIR to /work/NAG_f95 things will >> probably work much better for you. > > No, that doesn't seem to be the problem. If I provide the additional > --with-f95 option with the correct directory to configure, > I still get the same errors (although it mentions /work/NAG_f95/lib/ >
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
2006 Nov 25
0
[LLVMdev] f95 problem with SPEC2K
On 25 Nov 2006, at 09:02, Reid Spencer wrote: > Anyone know what to do about this: > > make[4]: Leaving directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/173.applu' > make[4]: Entering directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/178.galgel' > /usr/bin/f95 -w -S -O2 /opt/spec/CPU2000v1.3.1/benchspec// > CFP2000/178.galgel/src/modules.f90
2009 Dec 24
2
[LLVMdev] Problem in External/SPEC/CFP2000/177.mesa/Makefile ?
Hello folks, The makefile for 177.mesa says that for a small problem size, it will get 100 frames. But in the spec sources I have, the test folder only contains numbers for 10 frames: $ speccpu2000/benchspec/CFP2000/177.mesa/data $ wc -l test/input/numbers 10 test/input/numbers Generating 100 frames causes undefined behaviour because the program is doing unchecked fscanf on that
2011 Nov 23
1
[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4
In response to: > Date: Wed, 23 Nov 2011 18:24:16 +0100 > From: Duncan Sands <baldrick at free.fr<mailto:baldrick at free.fr>> > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to > LLVM 3.0rc4 > To: llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> > Hi Kevin, >> Since I don't have llvm-gcc installed, I tried to do the
2009 Dec 24
0
[LLVMdev] Problem in External/SPEC/CFP2000/177.mesa/Makefile ?
On Dec 23, 2009, at 6:26 PM, Julien Lerouge wrote: > Hello folks, > > The makefile for 177.mesa says that for a small problem size, it will > get 100 frames. But in the spec sources I have, the test folder only > contains numbers for 10 frames: > > $ speccpu2000/benchspec/CFP2000/177.mesa/data $ wc -l test/input/ > numbers > 10 test/input/numbers > >
2006 Aug 09
0
[LLVMdev] compiling SPEC suite using f95
> I managed to solve this problem myself.... The problem was not correctly specifiying the SPEC CPU2000 source directory. configure says the dir was found, but that doesn't mean the sources will be found. For future reference: When you get the error: make[2]: *** No rule to make target `Output/accum.rbc', needed by `Output/177.mesa.linked.rbc'. Stop. You've probably