similar to: [LLVMdev] r57326 malfunctions?

Displaying 20 results from an estimated 700 matches similar to: "[LLVMdev] r57326 malfunctions?"

2008 Nov 01
0
[LLVMdev] llvm-gcc-4.2 CC1_SPECS
On Fri, 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++/ >>
2008 Oct 31
3
[LLVMdev] gfortran link failure in current llvm svn
On Oct 30, 2008, at 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++/
2008 Oct 31
5
[LLVMdev] gfortran link failure in current llvm svn
Chris and Bill, I have tested the proposed patch from... http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016490.html under i686-apple-darwin9 and it solves the problems building 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
2008 Oct 31
0
[LLVMdev] gfortran link failure in current llvm svn
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
2008 Oct 31
0
[LLVMdev] gfortran link failure in current llvm svn
On Thu, Oct 30, 2008 at 5:23 PM, Jack Howarth <howarth at bromo.msbb.uc.edu> wrote: > Chris and Bill, > I have tested the proposed patch from... > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016490.html > > under i686-apple-darwin9 and it solves the problems building gfortran > from llvm svn. The resulting compiler works fine so can we get that > patch
2008 Oct 31
1
[LLVMdev] gfortran link failure in current llvm svn
On Thu, Oct 30, 2008 at 05:38:30PM -0700, Bill Wendling wrote: > On Thu, Oct 30, 2008 at 5:23 PM, Jack Howarth <howarth at bromo.msbb.uc.edu> wrote: > > Chris and Bill, > > I have tested the proposed patch from... > > > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016490.html > > > > under i686-apple-darwin9 and it solves the problems
2009 Jan 19
5
[LLVMdev] llvm/llvm-gcc-4.2 svn still produces -Wformat/-Wformat-security
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
2009 Jan 19
0
[LLVMdev] llvm/llvm-gcc-4.2 svn still produces -Wformat/-Wformat-security
Hi Jack, Because of the new changes and the fact that we have only 2 days before branching for 2.5, please retest the Fortran 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
2008 Oct 31
0
[LLVMdev] gfortran link failure in current llvm svn
On Oct 31, 2008, at 9:44 AM, Devang Patel wrote: >>> f951: warning: command line option "-Wformat" is valid for C/C++/ >>> ObjC/ObjC++ but not for Fortran > Try this not so elegant and untested patch. I'd not expect this to work for Ada, java or Pascal.
2009 Jan 19
0
[LLVMdev] llvm/llvm-gcc-4.2 svn still produces -Wformat/-Wformat-security
On Jan 18, 2009, at 5:11 PM, Jack Howarth 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++
2009 Jan 19
1
[LLVMdev] llvm/llvm-gcc-4.2 svn still produces -Wformat/-Wformat-security
Bill Wendling wrote: > Hi Jack, > > Because of the new changes and the fact that we have only 2 days > before branching for 2.5, please retest the Fortran front end as soon > as you can to see if the problem has been resolved. Hi Bill. Thanks for working on this! Unfortunately, I'm getting this warning now: $ llvm-g++ helloworld.c cc1plus: warning: -Wformat-security
2010 Oct 06
2
[LLVMdev] dragonegg vs -ffast-math?
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
2006 Nov 25
2
[LLVMdev] f95 problem with SPEC2K
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'
2012 May 05
1
f951.exe: sorry, unimplemented: 64-bit mode not compiled
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
2006 Sep 01
2
[LLVMdev] gfortran: patch, question
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 any rules I should be following.
2010 Oct 06
0
[LLVMdev] dragonegg vs -ffast-math?
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' >
2006 Oct 22
1
Problem with installing Hmisc and Design: gfrotran: error
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 installation is cancelled. I tried solving the problem through googling it, and
2012 May 10
1
Problems with 64bit dll compile in R-2.15.0
I built my package under the R version 2.14.1 on windows without any problems by first checking for issues using R CMD check (no warnings) and then R CMD build to build the tar.gz. I can install this on version 2.14.1 using install.packages(...). I next tested to see if I could also install on version 2.15.0 (also on my computer) using install.packages() with the version 2.14.1 tar.gz this
2014 Oct 01
2
[LLVMdev] Compiling As Obj-C or Obj-C++ On Windows
I have some C++ source files that mix in small bits of Obj-C. On the Mac, these files are marked to be compiled as Obj-C++. Looking at the clang help, it seems that the option for that is "-ObjC++". However, when I add that in Additional Options I get an error message: CL> : error : invalid integral value 'bjC++' in '-ObjC++' I see this same message if I put
2006 Sep 01
0
[LLVMdev] gfortran: patch, question
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