Kenneth Hoste
2006-Aug-31 17:46 UTC
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 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 sounds like differences in NAG version. I'm using 5.0(400). > Perhaps newer versions broke our makefile. > > If you'd like to investigate what is required to make it work with > NAG 5.1, and modify Makefile.nagfortran as appropriate, we can > merge it back into mainline adding code that autodetects the nag > version and does the right thing. >Bummer. I think I'll contact the NAG support for more info on this. Can you show me the content of your Makefile.nagfortran? Also, it is possible to tell make only to compile benchmark X? How can I enforce this? I'll try and get to the bottom of this. My evaluation period of the NAG compiler ends next week though... I'll hope I can figure it out before that time. 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
Chris Lattner
2006-Aug-31 21:46 UTC
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 -- http://nondot.org/sabre/ http://llvm.org/
Kenneth Hoste
2006-Sep-01 08:05 UTC
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 >> 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/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/kehoste/ work/LLVM/1.8/llvm/include -I/home/kehoste/work/LLVM/1.8/llvm/ projects/llvm-test/include -I../../../../include -I/home/kehoste/work/ LLVM/1.8/llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -I /work/ SPEC_CPU2000_1.3_src/benchspec/CFP2000/168.wupwise/src/ -I/work/ NAG_f95/lib -O3 -S dcabs1.c -o Output/dcabs1.ll -emit-llvm In file included from /work/SPEC_CPU2000_1.3_src/benchspec/ CFP2000/168.wupwise/src/dcabs1.f:1: /work/NAG_f95/lib/f95.h:109: error: syntax error before ‘Logical4’ /work/NAG_f95/lib/f95.h:109: warning: data definition has no type or storage class /work/NAG_f95/lib/f95.h:118: error: syntax error before ‘Integer4’ /work/NAG_f95/lib/f95.h:118: warning: data definition has no type or storage class This seems to suggest something is wrong with the f95.h file provided by NAG. This would be very strange, since I can't imagine them releasing something without thorough testing on a common platform (Linux/x86). I've mailed the support, but their reply seems to be quite slow... 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
Reasonably Related Threads
- [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
- [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
- [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
- [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
- [LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode