search for: f95

Hello, I tried to compile v2.3.1 on Solaris x86 with SUN Pro compilers. I had an error while stats libarary was being compiled and I notice that "-xtarget=generic64" was not passed to f95 while cc used it. Could you tell me how to fix this problem? f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sgram.f -o sgram.o f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sinerp.f -o sinerp.o f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sslvrg.f -o sslvrg.o f95...

...and this part. R directory: I put my *.R files here. One of these files calls upon a Fortran 95 subroutine with .Fortran("MySubroutine", var1=as.double(x), var2=as.double(y), etc.) I understand this part. src directory: I put my *.f95 files here. Also, I put a Makevars file here. Suppose that I have two *.f95 files, named CalculatorModule.f95 and ANiceSubroutine.f95. CalculatorModule.f95 contains a Fortran 95 module. ANiceSubroutine.f95 uses the functions in Calculator.Module.f95 with the...

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: error: unrecogniz...

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

...v 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: unrecognized gcc debugging opti...

...nneth, On Sat, 2006-11-25 at 10:12 +0100, Kenneth Hoste wrote: > > > > ? > > > > This man page: > > http://www.die.net/doc/linux/man/man1/gfortran.1.html > > > > says there's no such option as -kind > > > > Do I need some special version of f95 to run the SPEC2K tests? > > If I'm correct, f95 has nothing to do with GCC. As I just discovered, gfortran creates 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,...

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

...er we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking whether gcc needs -traditional... no checking how to run the C preprocessor... gcc -E defining F77 to be f95 checking whether we are using the GNU Fortran 77 compiler... no checking whether f95 accepts -g... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes ... skip checking for f95 option to produce PIC... -fPIC checking if f95...

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

...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 subdirectory of llvm-test/External/SPEC. My setup: LLVM-1.8 with the gcc4 frontend (gcc-4.0.1). The NAG f95 compiler is v5.1(216). My platform is Fedora Core 4 on a Intel Pentium 4. I was confronted with 6 different errors for the various benchmarks, 4 of which are relate to the NAG f95 compiler. See below for details. I seems most of the error are directly related to f95, which seems to have unde...

...11:02 PM, Chris Lattner wrote: > On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: >> ps We do have one oddity left in llvm-gfortran from current llvm >> svn. I find everytime I compile something with llvm-gfortran that >> I get a series of warning messages... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/ >> ObjC/ObjC++ but not for Fortran >> f951: warning: command line option "-Wformat-security" is valid for >> C/C++/ObjC/ObjC++ but not for Fortran >> f951: warning: command line option "-W...

Hi all, I'm preparing a package which uses .Fortran to interface a Fortran 95 function. This F95 function simply receives the name of a file from R, opens this file and forwards its content to a F95 module, which, in turn, makes the real computation. The F95 module is a pre-existing one and I'm trying to use it in its actual state. Thus, data transfer between R and this F95 module is mad...

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

...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 What does this print? $ grep F95 .../projects/llvm-test/Makefile.config ? > I then cd into llvm-test/External/SPEC and run m...

...e solved, new ones arised... Getting closer though... The fixes for the previous problems are at the bottom of this email, bug reports will be submitted when all problems are solved. +++ New/remaining problems +++ Currently, 9/26 benchmarks compile and run succesfully. One (fma3d) 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....

Hi, all, We just got the Sun Performance Library for our Suns running Solaris 2.6, and I read the relevant section of the "R Installation and Administration Manual" about configuring R to use BLAS. The manual suggests you must use Sun's "cc" and "f95" (maybe "f90"?) compilers in order to use the Performance Library. We have "cc" but not "f95". Would we be better off buying "f95", or compiling our own BLAS using ATLAS and our usual "gcc"/"g77" Gnu compilers? Has anyone succes...

On 31 Aug 2006, at 07:58, Chris Lattner wrote: > 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...

...between NAG 5.0 and 5.1, because I *do* want you to be successful. If NAG doesn't work, perhaps you could contribute to getting gfortran up and running. -Chris > +++ New/remaining problems +++ > > Currently, 9/26 benchmarks compile and run succesfully. One (fma3d) > 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...

On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: > ps We do have one oddity left in llvm-gfortran from current llvm > svn. I find everytime I compile something with llvm-gfortran that > I get a series of warning messages... > > f951: warning: command line option "-Wformat" is valid for C/C++/ > ObjC/ObjC++ but not for Fortran > f951: warning: command line option "-Wformat-security" is valid for > C/C++/ObjC/ObjC++ but not for Fortran > f951: warning: command line option "-Wno-format-ext...

Hi all, (Originally posted to r-help) I'm porting a package that I've worked on for OS X to Windows. The package is written in F95 so I need to compile it with gfortran and link it with gcc4. I've been trying to build an R with gcc4 without luck so far. If there is a binary of such a thing info would be appreciated. This package requires a Makefile. My question is, how can I find out (or what is), the link command? Here...