similar to: [LLVMdev] llvm-gcc-4.2 and gfortran

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

I've created fink packaging for a building the llvm and llvm-gcc-4.2 svn pulls under fink on Mac OS X. Hopefully the fink info script and patch should be clear enough for some comments on my build approach. The llvm-gcc and llvm-g++ compilers seem okay so far. The llvm-gfortran compiler seems to always spew a warning.. WARNING: 128-bit integers not supported! ...even when just compiling a

What exactly are the current limitations for using -O4 to create shared libraries with llvm/llvm-gcc-4.2 2.5? I tried a build of xplor-nih at -O4 with llvm-gcc, llvm-g++ and llvm-gfortran. The build fails to link shared libraries with errors such as... Building xplor-nih for platform: Darwin_9_x86 [ -d /Users/howarth/xplor-nih-2.21/bin.Darwin_9_x86/ ] || mkdir

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

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

Hello, Jack. > the libgfortran directory. Thanks in advance for any > information as I am working on test fink packaging for > llvm-gcc42. The gfortran is more or less ok nowadays. There are few patches waiting in my queue, but I'll commit them soon. It seems, that llvm-gfortran can compile almost all SPEC and polyhedron (there are few known issues, though). Unfortunately, I

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

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 \

On Mon, Jan 19, 2009 at 2:05 PM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: > 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. Yay! Thanks for testing this out. > Native configuration is i686-apple-darwin9 >

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 **, +

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:

Duncan, Actually, shouldn't this be just an error in the Makefile.in or Makefile.am? Why should a link line like... 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 \

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

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

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:

Anton, Doh! It appears that *-*-darwin* is preset in configure to not build libgfortran... # APPLE LOCAL end ARM darwin target powerpc-*-darwin* | i[3456789]86-*-darwin*) noconfigdirs="$noconfigdirs bfd binutils ld gas opcodes gdb gprof" noconfigdirs="$noconfigdirs sim target-rda" # LLVM LOCAL begin noconfigdirs="$noconfigdirs target-boehm-gc

Hi Jack, > The curent llvm svn (r54623) is unable to link the gfortran > compiler in llvm-gcc-4.2 svn. I am getting the error... ... > Undefined symbols: > "_create_init_utf16_var", referenced from: > _darwin_build_constant_cfstring in libbackend.a(darwin.o) this is probably due to recent Apple changes. Fortran builds on linux. > Why is c++ being used

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':

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

Is anyone able to bootstrap llvm-gcc42 svn on x86_64-apple-darwin10? Currently it is failing here with... /sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/xgcc -B/sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/ -B/sw/lib/llvm-gcc-4.2/x86_64-apple-darwin10/bin/ -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes