similar to: [LLVMdev] compiling SPEC suite using f95

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/

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

> 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

Hello LLVM-people, 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). Unfortunately the f2c compiler only allows the translation of Fortran-77 programs to C code (which is then compiled using llvm-gcc).

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

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

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

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 >

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:

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

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

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

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'

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

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

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

Please file a bug for this. Thanks, Tanya On Wed, 9 Aug 2006, Kenneth Hoste wrote: >> > 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]:

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

Hi Scott, On 18 Mar 2007, at 04:22, Scott Fortmann-Roe wrote: > Hi, > > I noticed that LLVM had signed up as a mentoring organization for > Google's summer of code. LLVM looks like an exciting project that > overlaps some of my interests. > > I would be interested in developing an additional front end for a > language it does not currently support (I'm open to

Hello, I have been trying to compile spec benchmark with llvm.I am trying the 2 methods suggested but have not succeeded yet . 1) Setting the flags -Wl,-native-cbe or -Wl,-native flags to llvm-gcc. This results in successful compilation with llvm BUT it doesn't create .bc files (?)which I need for my experimentation.Any other significant modification/addition missing ?? 2) Using llvm-test :