search for: f951

...ding gfortran from llvm svn. The resulting compiler works fine so can we get that patch in before 2.4 is release? Jack 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-extra-args" is valid fo...

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

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

...g compiler works fine so can we get that > patch in before 2.4 is release? I applied it to mainline. > 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-extra-args" i...

Hello: Under my Windows 7 system, "R CMD check DiercxkSpline_1.1-5.tar.gz" fails because: f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [bispev.o] Error 1 gfortran -m64 -O2 -mtune=core2 -c bispev.f -o bispev.o f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [bispev.o] Error 1 ERROR: compilation failed for package 'DierckxSpline'...

.../* APPLE LOCAL AltiVec */ It would seem obvious that this last patch must not really be functional since gfortran is being given this formatting flags by default. I think this may not be obvious for the other compilers since they don't complain if these flags are present like gfortran does... 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-extra-args" is valid fo...

...> patch in before 2.4 is release? > > I applied it to mainline. > > > 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-extra-ar...

The current llvm/llvm-gcc-4.2 svn when built on i686-apple-darwin9 still produces the bogus warnings... 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 whenc compling any code with gfortran. This causes the gfortran testsuite in gcc...

I am finding that llvm 2.8 rc3 with dragonegg svn built against current gcc-4_5-branch doesn't appear to allow gfortran to use -ffast-math. Attempting to compile code using the dragonegg plugin under gcc 4.5.2 with that option produces the error... f951: Unknown command line argument '--enable-finite-only-fp-math'. Try: 'f951 -help' The standard gcc 4.5.2 gfortran compiler has no problem with that option. Jack

...C/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: unrecognized command line option "-fixed" make[4]: *** [modules.c] Error 1 ? This man page: http://www.die.net/doc/linux/man/man1/gfortran.1.html says there's no such opt...

...Oct 31, 2008 at 10:38:50AM -0700, Mike Stump wrote: > On Oct 31, 2008, at 9:40 AM, Jack Howarth wrote: >> However in current llvm svn, when I compile code with llvm-gfortran, I >> get these warning >> flags passed by default so that I get bogus warnings of... >> >> 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 "...

Hi, I have a first quick patch and a question. The patch links f951 with g++ when LLVM is enabled. It's at the end of this email. I wanted to know if I should submit patches with comments around them like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to the tree. I'd like to make it as easy as possible to apply these, so let me know...

Hi Jack, > I am finding that llvm 2.8 rc3 with dragonegg svn built against current > gcc-4_5-branch doesn't appear to allow gfortran to use -ffast-math. Attempting > to compile code using the dragonegg plugin under gcc 4.5.2 with that option produces the error... > > f951: Unknown command line argument '--enable-finite-only-fp-math'. Try: 'f951 -help' > > The standard gcc 4.5.2 gfortran compiler has no problem with that option. > Jack I've fixed this in commit 115781. The fix will be in the dragonegg 2.8 release, which should...

cannot exec 'f951': No such file or directory Reply-To: Hi all, I'm using R on an Suse Linux system. Since Hmisc and Design need both fortran, I installed gfortran (through rpm). However, I still get an error message, namely: gfrotran: error cannot exec 'f951': No such file or directory And the...

...front end as soon as you can to see if the problem has been resolved. Thanks! -bw On Sun, Jan 18, 2009 at 5:11 PM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: > The current llvm/llvm-gcc-4.2 svn when built on > i686-apple-darwin9 still produces the bogus warnings... > > 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 > > whenc compling any code with gfortran. This causes the gfortran te...

...Clock skew detected. Your build may be incomplete. installing to H:/Desktop/PkgBuild/BlossomPkg.Rcheck/Blossom/libs/i386 *** arch - x64 make: Warning: File `InternalFcts.f90' has modification time 0.52 s in the future gfortran -m64 -O2 -mtune=core2 -c InternalFcts.f90 -o InternalFcts.o f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [InternalFcts.o] Error 1 gfortran -m64 -O2 -mtune=core2 -c InternalFcts.f90 -o InternalFcts.o f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [InternalFcts.o] Error 1 ERROR: compilation failed for package ...

...tering 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: unrecognized command line option "-fixed" > make[4]: *** [modules.c] Error 1 > > ? > > This man page: > http://www.die.net/doc/linux/man/man1/gfortra...

On Fri, 1 Sep 2006, Michael McCracken wrote: > Hi, I have a first quick patch and a question. The patch links f951 > with g++ when LLVM is enabled. It's at the end of this email. Thanks, applied! > I wanted to know if I should submit patches with comments around them > like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to > the tree. I'd like to make it as easy as p...

...igure: error: in `/home/lotayv01/R-2.11.1': configure: error: cannot compile a simple Fortran program See `config.log' for more details. For more details I can show you the section in the config.log file ... /data/home/lotayv01/usr/local/gfortran/bin/../libexec/gcc/i686-pc-linux-gnu/4.6.0/f951: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory configure:22471: $? = 1 configure: failed program was: | program main | | end configure:22548: WARNING: compilation failed configure:22554: result: configure:22556: checking f...

...2 svn. I am getting the error... c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \ fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o fortran/data.o fortran/decl.o fortran/dump-parse-tree.o fortran/error.o fortran/expr.o fortran/interface.o fortran/intrinsic.o fortran/io.o fortran/iresolve.o fortran/match.o fortran/matchexp.o fortran/misc.o fortran/module.o fortran...