This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/33271] nint_2.f90 abort compiled with -O0
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Sep 2007 14:25:26 -0000
- Subject: [Bug fortran/33271] nint_2.f90 abort compiled with -O0
- References: <bug-33271-14842@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from burnus at gcc dot gnu dot org 2007-09-03 14:25 -------
> > One last question: in your build tree, you should have a file named
> > ${builddir}/${target_triplet}/libgfortran/config.h. How does it define the
> > macros HAVE_LLROUND, HAVE_LLROUNDF, HAVE_LLROUNDL, HAVE_LROUND, HAVE_LROUNDF
> > and HAVE_LROUNDL?
>
> That last question seems beyond my ken. I am running glibc-2.6.1
> (the latest official).
That file should be in your case in
/var/tmp/43/build-159/powerpc-unknown-linux-gnu/libgfortran/config.h
^^^^^^^^^^^^ <- this might be different,
depending where you build gcc/gfortran; this was the
directory used in your bug description (comment #0)
The file is generated at configure time and thus specific to the system where
gcc/gfortran is build.
On my system (x86_64-unknown-linux-gnu, but also glibc-2.6), I have in the
equivalent file:
#define HAVE_LLROUND 1
#define HAVE_LLROUNDF 1
#define HAVE_LLROUNDL 1
#define HAVE_LLROUND 1
#define HAVE_LLROUNDF 1
#define HAVE_LLROUNDL 1
I would expect that your config.h has the same entries (as we both use a recent
glibc), but it would be great if you could confirm this.
> The question is with which C compiler ( the latest Trunk, gcc-4.3.0?
> 4.1.current? 3.3.6 ? or 3.4.6? and even the junky 4.2.1)
As FX wants to check whether the C Library (glibc) works correctly, it should
not matter; but if you have the choice I would use gcc 4.3.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33271