search for: galgel

...still has a f95 related problem (see below). The other 16 are divided into two groups: *** 1) *** bytecode builds ok, but exection fails For 10 benchmarks the execution fails as follows: JIT problems: <start> Running: /home/kehoste/work/LLVM/1.8/llvm/projects/llvm-test/ RunSafely.sh 500 galgel.in galgel.out /home/kehoste/work/LLVM/1.8/ llvm/Release/bin/lli -force-interpreter=false ../178.galgel.llvm.bc (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) Core was generated by `/home/kehoste/work/LLVM/1.8/llvm/Relea...

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' f951: warning: unrecognized gcc debugging option: u f951: warning: unrecognized gcc debugging option: u f951:...

...t;/lib. This should probably be fixed in the Makefile.nagfortran, but I don't know how (since there's no other *dylib file available it seems). This only generates a warning from gccld, but I think it's the cause of the problems which are reported subsequently. Affected benchmarks: galgel, facerec, sixtrack *** BEAM (fma3d) There seem to be some issues with the fma3d benchmark, when translating from Fortran to C: f95 -w -S -O2 <path>/SPEC_CPU2000_1.3_src/benchspec/CFP2000/191.fma3d/ src/beam.f90 -o beam.c -dusty -maxcontin=69 Error: <path>/SPEC_CPU2000_1.3_src/benc...

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

...> The other 16 are divided into two groups: > > *** 1) *** bytecode builds ok, but exection fails > > For 10 benchmarks the execution fails as follows: > > JIT problems: > <start> > Running: /home/kehoste/work/LLVM/1.8/llvm/projects/llvm-test/ > RunSafely.sh 500 galgel.in galgel.out /home/kehoste/work/LLVM/1.8/ > llvm/Release/bin/lli -force-interpreter=false ../178.galgel.llvm.bc > (no debugging symbols found) > Using host libthread_db library "/lib/libthread_db.so.1". > (no debugging symbols found) > Core was generated by `/home/kehoste/...

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

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 -o modules.c -fixed -kind=byte - > dcfuns -dusty > f95: unrecognized option '-kind=byte' > f951: warning: unrecognized gcc debugging option: u > f951: warning: unrecogn...

...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 'libf97.dylib' isn't in my NAG_f95/lib directory, and nothing > remotely like it either. > > Are some major changes in the NAG For...

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

...29% -9.31% 172.mgrid 2007 1917 1982 4.69% 1.26% 21272 21224 23086 0.23% -7.86% 173.applu 3445 3285 3241 4.87% 6.29% 67164 67124 63130 0.06% 6.39% 177.mesa 3612 2752 3597 31.25% 0.42% 570567 590889 561250 -3.44% 1.66% 178.galgel 6637 6809 6617 -2.53% 0.30% 225564 225583 233742 -0.01% -3.50% 179.art 6710 5219 5588 28.57% 20.08% 25111 24188 28126 3.82% -10.72% 183.equake 5247 4813 5118 9.02% 2.52% 32539 34011 31431 -4.33% 3.53% 187.facerec 4332 4...

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

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

...29% -9.31% 172.mgrid 2007 1917 1982 4.69% 1.26% 21272 21224 23086 0.23% -7.86% 173.applu 3445 3285 3241 4.87% 6.29% 67164 67124 63130 0.06% 6.39% 177.mesa 3612 2752 3597 31.25% 0.42% 570567 590889 561250 -3.44% 1.66% 178.galgel 6637 6809 6617 -2.53% 0.30% 225564 225583 233742 -0.01% -3.50% 179.art 6710 5219 5588 28.57% 20.08% 25111 24188 28126 3.82% -10.72% 183.equake 5247 4813 5118 9.02% 2.52% 32539 34011 31431 -4.33% 3.53% 187.facerec 4332 4...