similar to: (no subject)

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

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

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

I'm on R 2.1.0. In the "source" function there is a bug preventing the proper use of the chdir option (which simply doesn't work). The problem is that in the function the following line occurs: file <- file(file, "r", encoding = encoding) This overwrites the variable "file" and later causes the check if (chdir && is.character(file)

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

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

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

Looking back through the commits to llvm-gcc-4.2/trunk/gcc/config/i386/darwin.h, I see a total backout of format related warnings in r56923 followed by the reapplication of r569065 with a fix (r56946)... -- llvm-gcc-4.2/trunk/gcc/config/i386/darwin.h 2008/10/01 17:38:40 56923 +++ llvm-gcc-4.2/trunk/gcc/config/i386/darwin.h 2008/10/02 06:16:08 56946 @@ -101,6 +101,8 @@ %{!mmacosx-version-min=*:

Dear all, in an LDA analysis with n groups n-1 LD functions result. Implicitly this defines an LD fucntion for the last group. Does there exist code already to explictly construct this LD function? Thanks, Stefan

Current dragonegg svn builds against llvm svn again, but the resulting dragonegg plugin fails at runtime. When either c or fortran is compiled against either gcc-4.5.3 or gcc-4.6.1, the compilations fail as... cc1: Unknown command line argument '--code-model=default'. Try: 'cc1 -help' cc1: Did you mean '-fast-isel=default'?

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.

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'

Hi David/Renato, By AST I mean Abstract Syntax Tree. We are writing an optimization pass for some FORTRAN95 + MPI code that requires us to analyze the AST. We thought of 2 ways of doing this: 1. Compile the code using Clang/llvm-gfortran, get the textual AST dump (somehow), analyze the AST dump using Ruby, modify it and then feed back the modified AST to LLVM. 2. Do the analysis as an LLVM

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

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

Hi Jack, > Current dragonegg svn builds against llvm svn again, but the resulting > dragonegg plugin fails at runtime. When either c or fortran is compiled > against either gcc-4.5.3 or gcc-4.6.1, the compilations fail as... > > cc1: Unknown command line argument '--code-model=default'. Try: 'cc1 -help' > cc1: Did you mean '-fast-isel=default'? I

The curent llvm svn (r54623) is unable to link the gfortran compiler in llvm-gcc-4.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 \

Hello, I have basic familiarity with Unix but by most standards a novice. I am trying to install R on a linux machine and am following the instructions in the R install and admin guide in terms of what is required to compile the R source code. I downloaded R version 2.11.1 and extracted the files into my home directory. I realize I need a FORTRAN compiler to help with this process and have

On 9/1/06, Chris Lattner <sabre at nondot.org> wrote: > On Fri, 1 Sep 2006, Michael McCracken wrote: > > 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

On x86-64 linux, in stage 2, I get: c++ -g -O2 -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 -fno-common -DHAVE_CONFIG_H -o f951 \ fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o fortran/data.o fortran/decl.o