search for: nagware

...fore numeric 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 fil...

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

...s_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 i...

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

...x 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 &...

...ome special version of f95 to run the SPEC2K tests? If I'm correct, f95 has nothing to do with GCC. GCC has the gfortran compiler, but this is a Fortran-to-binary compiler. You want the NAG f95 compiler, which allows Fortran-to-C translation, what you appear to be doing. http://www.nag.co.uk/nagware/np.asp (it's commercial, but I think at least Chris has a license for 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:...

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

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

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'

...ates an f95 symbolic link to gfortran when it is installed. > GCC has the gfortran compiler, but this is a Fortran-to-binary compiler. > You want the NAG f95 compiler, which allows Fortran-to-C translation, > what you appear to be doing. Yes, I believe I do. > http://www.nag.co.uk/nagware/np.asp (it's commercial, but I think at > least Chris has a license for this). It seems our "sanity check" in configure for f95 isn't correct. Its checking for NAG f95, not gfortran. However, the sanity check "passed" on the gfortran link for f95. I'll fix tha...

...9;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/projects/llvm-test/ External/SPEC/CFP2000/168.wupwise -I/home/kehoste/work/LLVM/1.8/llvm/ projects/llvm-test/External/SPEC/CFP2000/168.wupwise -I/home/k...

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

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

...pr node 47050 type 414 in tree flattener Internal Error -- please report this bug Again, this is no job for the LLVM people. Affected benchmarks: apsi *** libf97.dylib not found ...simply because it's not on my system. I guess this changed in the 5.1 release of f95. Also, there's no NAGWare subdirectory of the lib directory, which should be the case according to the NAG documentation. It seems the libraries are directly located in <path>/lib. This should probably be fixed in the Makefile.nagfortran, but I don't know how (since there's no other *dylib file available i...