llvm dev - Aug 2006 - [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 --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec  
>> -- without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/ 
>> work/NAG_f95/lib --with-f95-inc=/work/NAG_f95/lib --with-llvmsrc=/ 
>> work/LLVM/1.8/llvm --with-llvmobj=/work/LLVM/1.8/llvm
>
> What does this print?
>
> $ 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 ok to me...
>
>> I then cd into llvm-test/External/SPEC and run make to compile the  
>> benchmarks to LLVM bytecode. Make stops with the following error  
>> messages:
>>
>> /work/SPEC_CPU2000_1.3_src/benchspec/CFP2000/189.lucas/src/  
>> lucas_distrib_spec.f90:2995: error: syntax error before ‘(’ token
>
> Very strange.  Have you *looked* at the file?  Does it looks  
> reasonable? What's going on on that line?
>
> Have you tried to debug this at all?
>
>> Any further suggestions what might be wrong are welcome...  
>> Especially the /lib/NAGWare/... part puzzles me.. I did show with  
>> configure where the NAGWare lib dir is located, so why this error?
>
> I don't know, maybe your Makefile.config entries will shed light on  
> this.
>
>>> >  Also, with the new gcc4 frontend, it seems the Fortran issue
>>> will >  disappear in the near future (with the use of gfortran).
>>> Is that >  correct? Or will there
>>> >  be other problems?
>>>  Someone needs to do the work to test gfortran and fix any  
>>> problems it runs  into.  I'm not aware of anyone doing this,  
>>> though it's probably not hard.
>>
>> So, in the future it will be possible to use gcc/g++/gfortran to  
>> generate LLVM bytecode?
>
> Yes, if someone does the work.
This is just a single error appearing, I'm getting hundreds, if not  
thousands, of these error, for various benchmarks/files.

Which LLVM version is working for you with F95?

Kenneth

-- 

Statistics are like a bikini. What they reveal is suggestive, but  
what they conceal is vital (Aaron Levenstein)

Kenneth Hoste
ELIS - Ghent University
kenneth.hoste at elis.ugent.be
http://www.elis.ugent.be/~kehoste

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 ok to me...
It doesn't to me.  If you set F95_DIR to /work/NAG_f95 things will 
probably work much better for you.
> This is just a single error appearing, I'm getting hundreds, if not 
> thousands, of these error, for various benchmarks/files.
>
> Which LLVM version is working for you with F95?
LLVM 1.7+.

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/

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     := /work/NAG_f95/bin/f95
>> F95_INC := /work/NAG_f95/lib
>> F95_LIB := /work/NAG_f95/lib
>>
>> Looks ok to me...
>
> 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/ 
NAGWare/... not found as errors now).
It seems the paths in Makefile.nagfortran (in llvm-test) are  
hardcoded (lib/NAGWare/quickfit.o and such).

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 'libf97.dylib' isn't in my NAG_f95/lib directory, and
nothing remotely like it either.

Are some major changes in the NAG Fortran compiler itself the cause  
of this? Which version are you using? Which paths are present in the  
Makefile.nagfortran file?
I'm using the 5.1(216) release of f95.
>
>> This is just a single error appearing, I'm getting hundreds, if  
>> not thousands, of these error, for various benchmarks/files.
>>
>> Which LLVM version is working for you with F95?
>
> LLVM 1.7+.
Hmm, I'm using LLVM1.8 with the gcc4 frontend. I'm starting to get  
really frustrated by all this... :(

greetings,

Kenneth

-- 

Statistics are like a bikini. What they reveal is suggestive, but  
what they conceal is vital (Aaron Levenstein)

Kenneth Hoste
ELIS - Ghent University
kenneth.hoste at elis.ugent.be
http://www.elis.ugent.be/~kehoste