This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [patch] Allow building libgfortran as a DLL
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>
- Cc: FX <fxcoudert at gmail dot com>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Date: Tue, 04 Aug 2009 11:07:27 +0100
- Subject: Re: [patch] Allow building libgfortran as a DLL
- References: <20090803065932.GA6467@physik.fu-berlin.de>
Tobias Burnus wrote:
> FX wrote:
>> OK to commit?
>
> OK. I assume DaveK's regtests have finished by now and no problem has showed up.
There is one FAIL:
FAIL: gfortran.dg/atan2_1.f90 execution test
However this is a new test added 20090726 and I haven't run it with
statically-linked gfortran before; it might fail there too.
I took a quick step through it in the debugger. It's possibly an
excess-precision FP thing. Can you point me at what code in the gfortran
startup is meant to set the FP precision and rounding (etc.) modes?
> PS: Regarding DLL - or generally Windows: I remember some
> mailing list post (or c.l.f or gfortran-users@), which I could not find
> again, about issues under Windows with accessing the command line or I/O
> inquiry (is file open?). Does someone recall? It might have been using
> libgfortran functions from a DLL. I vaguely remember that another compiler
> (ifort?) included a special version of the Fortran run-time library for
> that reason.
Doesn't ring any bells here. If you dig something up let me know and I'll
help look at it.
cheers,
DaveK
--
(*) - http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg00418.html