similar to: gfortran and BLAS on AMD64 Linux

Hello, I am trying to call the BLAS Level1 function zdotc from R via a .C call like this: #include "R.h" #include "R_ext/BLAS.h" void testzdotc() { Rcomplex zx[3], zy[3], ret_val; zx[0].r = 1.0; zx[0].i = 0.0; zx[1].r = 2.0; zx[0].i = 0.0; zx[2].r = 3.0; zx[0].i = 0.0; zy[0].r = 1.0; zy[0].i = 0.0; zy[1].r = 2.0; zy[0].i = 0.0; zy[2].r = 3.0;

I'm developing some software and running into compiling warning: conditionals.c:104: warning: passing argument 4 of 'dger_' discards qualifiers from pointer target type conditionals.c:104: warning: passing argument 6 of 'dger_' discards qualifiers from pointer target type the netlib documentation states that the arguments x and y should be unchanged on exit. Should should

R-help - This code iterates over a function with 2 free parameters to find a list of values (which are the number of incorrect predictions for a computational model). I want to find the values of i,e when there is the minimum number of incorrect predictions. In other words, the value of "i" and "e" when variable "thesum" is at the lowest possible number. The

Hi, gfortran trunk and 9-branch now have an option to automatically generate C prototypes for old-style F77 procedures. I just did for a in *.f; do gfortran -fsyntax-only -fc-prototypes-external $a > ${a%.f}.h; done in the src/modules/lapack directory. This generates header files which contain prototypes like int ilaenv_ (int *ispec, char *name, char *opts, int *n1, int *n2, int *n3,

Hi I've got two builds of R, one using g77 (version 3.4.6) and the other using gfortran (version 4.1.2). The two builds are otherwise identical as far as I can tell. The one which used g77 performs crossprod()s roughly twice as fast as the gfortran one. I'm wondering if this rings a bell with anyone, and if so, are you aware of any configure settings which will improve the performance

Building llvm 2.3 and llvm-gcc4.2-2.3 on Mac OS X 10.5, I am seeing the following failures remaining in the gcc 4.2.1 gfortran testsuite... LAST_UPDATED: Native configuration is i686-apple-darwin9 === gfortran tests === Running target unix FAIL: gfortran.dg/actual_array_constructor_1.f90 -O1 execution test FAIL: gfortran.dg/actual_array_constructor_1.f90 -O2 execution test FAIL:

Using the proposed patch for enabling the i386 multilib under the x86_64-apple-darwin build... http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-August/025040.html the following gfortran testsuite results are obtained... Native configuration is x86_64-apple-darwin10 === gfortran tests === Running target unix/-m32 FAIL: gfortran.dg/aint_anint_1.f90 -O (internal compiler error) FAIL:

Building the prerelease of llvm-gcc 2.4 on Intel darwin9 with the following patch... --- llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c.org 2008-10-30 18:55:45.000000000 -0400 +++ llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c 2008-10-30 18:57:29.000000000 -0400 @@ -157,3 +157,27 @@ { gcc_assert(0); } + + +bool cvt_utf8_utf16 (const unsigned char *, size_t, unsigned char **, +

OK: despite Dirk's very kind help, I decided that trying to deal with R configuration and Debian configuration simultaneously was too difficult. I did manage to solve my problem by reconfiguring/making/ installing all of 2.3.1 from source: ./configure F77=/usr/bin/g77 make make install A few questions inspired by this experience: (1) it seems a bit odd that R sets F77=gfortran by

The current llvm/llvm-gcc4.2 svn is now fixed with respect to the extra warnings that were being emitted by the gfortran compiler. The gfortran testsuite results under Intel Darwin9 are appended below. Jack Native configuration is i686-apple-darwin9 === gfortran tests === Running target unix/-m32 FAIL: gfortran.dg/aint_anint_1.f90 -O (internal compiler error) FAIL:

From the configure output of the latest devel snapshot: > checking for g77... no > checking for f77... no > checking for xlf... no > checking for frt... no > checking for pgf77... no > checking for fl32... no > checking for af77... no > checking for fort77... no > checking for f90... no > checking for xlf90... no > checking for pgf90... no > checking for

I recently upgraded to Rtools28 to build a package under Windows. I see that g77 is no longer in Rtools, but it does have gfortran, and it uses version: GNU Fortran (GCC) 4.2.1-sjlj (mingw32-2) I am compiling some old fortran code as part of a larger project. When I do that, I get undefined references: gcc.exe: s_cmp.o: No such file or directory gcc.exe: s_copy.o: No such file or directory

I've filed bugzilla reports for the gcc 4.2.1 gfortran testsuite failures in llvm/llvm-gcc-4.2 v2.3. These are... http://llvm.org/bugs/show_bug.cgi?id=2430 http://llvm.org/bugs/show_bug.cgi?id=2431 http://llvm.org/bugs/show_bug.cgi?id=2437 http://llvm.org/bugs/show_bug.cgi?id=2438 http://llvm.org/bugs/show_bug.cgi?id=2439 http://llvm.org/bugs/show_bug.cgi?id=2440

Hi, > I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit > Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04, > llvm-gfortran gave me following errors > > $ llvm-gfortran -Wall hello.f95 -o hellof this works here on x86-64 ubuntu 8.10. I took a look in my libgfortran.a and it doesn't reference any of the symbols you mention. >

Colleagues, I have a routine in package labdsv that calls a FORTRAN subroutine. Recently, I was informed that it sometimes gives different results on a PC and Mac, and that the PC version is clearly wrong. I tested it on linux (because I don't have a PC), and I get the same (incorrect) behavior as the PC. Simply by inserting debug WRITE statements in the FORTRAN I would get different,

Hi, I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04, llvm-gfortran gave me following errors $ llvm-gfortran -Wall hello.f95 -o hellof /home/jli127/LLVM/llvm-gcc/install/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.2.1/../../../../lib64/libgfortran.a(error.o): In function `_gfortrani_gfc_itoa':

I have a package with some embedded legacy FORTRAN code (for computing complex Bessel functions, written in 2003 by C. Bond to implement the algorithms of Zhang and Jin 1996). It worked well until recently [despite warnings about deprecated headers "includes at least one deprecated or antiquated header" -- when I tried to fix these the code stopped working, so I left them alone]. Now an

> rab45+ at pitt.edu wrote: >> Jerry, >> >> Here are the two R packages. >> >> Thanks. >> >> Rick > All the fortran codes compile OK so the problem is invoking the compiler > you > want. One approach which is a work around is to rename the gfortran > executable > to somthing else like gfortran-save and create a link called gfortran that

Hi Duncan, Thanks for your answers. Compiling .s file is OK after adding the -lgfortran -lgfortranbegin. I replace my Ubuntu 8.04 and by Ubuntu 8.10. And I checked all new packages installed by 'apt-get' are amd64 version. However after compiling the llvm-gfortran, I got the same error. Here is my configure arguments $ ../llvm-gcc4.2-2.3.source/configure --prefix=`pwd`/../install

Hi, > Here is my configure arguments > $ ../llvm-gcc4.2-2.3.source/configure --prefix=`pwd`/../install > --program-prefix=llvm- \ > --disable-shared --disable-multilib \ > --enable-llvm=/llvm/llvm-obj --enable-languages=c,c++,fortran this looks ok to me. It's essentially the same as what I use. Try with 2.4 (about to be released). I'm not sure I ever tried to build the