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 target-libffi"
noconfigdirs="$noconfigdirs target-libgfortran target-libjava"
noconfigdirs="$noconfigdirs target-libmudflap target-libobjc"
noconfigdirs="$noconfigdirs target-libssp target-libstdc++-v3
target-zlib"
# LLVM LOCAL end
;;
*-*-darwin*)
noconfigdirs="$noconfigdirs ld gas gdb gprof"
noconfigdirs="$noconfigdirs sim target-rda"
noconfigdirs="$noconfigdirs ${libgcj}"
# LLVM LOCAL begin
noconfigdirs="$noconfigdirs target-boehm-gc target-libffi"
noconfigdirs="$noconfigdirs target-libgfortran target-libjava"
noconfigdirs="$noconfigdirs target-libmudflap target-libobjc"
noconfigdirs="$noconfigdirs target-libssp target-libstdc++-v3
target-zlib"
# LLVM LOCAL end
;;
I'll try removing libgfortran from noconfigdirs. Also, I am using the
llvm-gcc-4.2
sources that I pulled with...
svn co http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk llvm-gcc-4.2
and these are currently at revision 45366. Are these the same sources that you
are using? Lastly, are there any issues with running the gcc testsuite
within the llvm-gcc-4.2 directories that I should be aware of? Thanks in
advance for any information.
Jack
On Dec 27, 2007, at 9:14 AM, Jack Howarth wrote:> Anton, > Doh! It appears that *-*-darwin* is preset in configure to > not build libgfortran...Ah, that should certainly be fixed. Please send in the obvious patch to the llvm-commits list (after verifying that it doesn't break the c/c ++/objc build), thanks Jack!> I'll try removing libgfortran from noconfigdirs. Also, I am using > the llvm-gcc-4.2 > sources that I pulled with... > > svn co http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk llvm- > gcc-4.2 > > and these are currently at revision 45366. Are these the same > sources that you > are using?Yep, that should be latest.> Lastly, are there any issues with running the gcc testsuite > within the llvm-gcc-4.2 directories that I should be aware of? > Thanks in > advance for any information.I think there are a number of failures, many of which are bogus/ useless (looking for GCC optimizer dumps that llvm-gcc doesn't run, for example), but it should run. Anton and Dale would know more. -Chris
On Dec 27, 2007, at 10:56 AM, Chris Lattner wrote:>> Lastly, are there any issues with running the gcc testsuite >> within the llvm-gcc-4.2 directories that I should be aware of? >> Thanks in >> advance for any information. > > I think there are a number of failures, many of which are bogus/ > useless (looking for GCC optimizer dumps that llvm-gcc doesn't run, > for example), but it should run. Anton and Dale would know more.Yes, although I have never tried Fortran. There are currently hundreds of failures in the C/C++ parts of the testsuites. Many are looking for microoptimizations that llvm doesn't currently do (especially with builtins), or gcc extensions/features that llvm doesn't support or doesn't support well (nested functions, exporting the address of labels, exotic inline assembly, profiling, debugging optimized code, etc.). Some more serious failures are structure layout incompatibilities, a known problem. You can probably expect a similar failure level in Fortran.