search for: nag_f95

...; 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/Make...

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

...te: >>> $ 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 provi...

...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 ? > I then cd into llvm-test/External/SPEC and run make to compile the...

...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 (the inc=.../lib part is correct, the headers files are indeed located in the lib dir of NAG f95). which returns the following messages concerning my s...

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

...n 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(21...

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/ > NAGWare/... n...

...le 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. OK, I seem to be getting closer to the problem... When compiling a single benchmark, I noticed the following... /work/NAG_f95/bin/f95 -w -S -O2 /work/SPEC_CPU2000_1.3_src/benchspec/ CFP2000/168.wupwise/src/dcabs1.f -o dcabs1.c -dusty -dcfuns Evaluation trial version of NAGWare Fortran 95 Release 5.1(216) /home/kehoste/work/LLVM/1.8/llvm-gcc4-1.8-x86-linux/bin/llvm-gcc - DSPEC_CPU2000 -I/home/kehoste/work/LLVM/1.8/llvm/p...

...x/x86. LLVM is configured using: ./configure --prefix=/path/to/bin/dir and compiled using gmake; gmake install Subsequently, llvm-test (which resides in llvm/TestSuite/llvm-test), is configured using: ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src --without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/work/NAG_f95/lib -- with-f95-inc=/work/NAG_f95/lib When running 'make VERBOSE=1' in llvm-test/External/SPEC, I get the following output: if [ ! -f CFP2000/Makefile ]; \ then \ /work/LLVM/1.7/llvm/autoconf/mkinstalldirs CFP2000; \ cp /work/LLVM/1.7/ll...

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