search for: quickfit

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

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

...eric constant /work/SPEC_CPU2000_1.3_src/benchspec/CFP2000/189.lucas/src/ lucas_distrib_spec.f90:2999: warning: data definition has no type or storage class make[2]: [Output/lucas_distrib_spec.o] Error 1 (ignored) g++ -o Output/189.lucas.native Output/lucas_distrib_spec.o -lm / lib/NAGWare/quickfit.o -Xlinker -flat_namespace /lib/NAGWare/ libf97.dylib /lib/NAGWare/libf96.a g++: Output/lucas_distrib_spec.o: No such file or directory g++: /lib/NAGWare/quickfit.o: No such file or directory g++: /lib/NAGWare/libf97.dylib: No such file or directory g++: /lib/NAGWare/libf96.a: No such file or dire...

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

...-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). Okay, well that's progress. > It seems the paths in Makefile.nagfortran (in llvm-test) are hardcoded > (lib/NAGWare/quickfit.o and such). ok > 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 'libf...

...na_rh90_282.tgz). > > *** libf97.dylib not found > It appears the *.dylib files are Mac specific. Apparently the usage of f95 was only tested on Mac (I think Chris did this?). Solution (for Linux/x86): modify Makefile.nagfortran: CPPFLAGS += -I$(F95_DIR)/lib LDFLAGS += $(F95_DIR)/lib/quickfit.o $(F95_DIR)/lib/libf98.so $ (F95_DIR) /lib/libf98.a I'll also submit a bug report for this one. 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.h...

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

...found >> > > It appears the *.dylib files are Mac specific. Apparently the usage > of f95 was only tested on Mac (I think Chris did this?). > > Solution (for Linux/x86): > > modify Makefile.nagfortran: > > CPPFLAGS += -I$(F95_DIR)/lib > LDFLAGS += $(F95_DIR)/lib/quickfit.o $(F95_DIR)/lib/libf98.so $ > (F95_DIR) /lib/libf98.a > > I'll also submit a bug report for this one. > > greetings, > > Kenneth > > -Chris -- http://nondot.org/sabre/ http://llvm.org/

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