This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
- From: "toon at moene dot indiv dot nluug dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 May 2005 18:49:31 -0000
- Subject: [Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
- References: <20050425082043.21203.corsepiu@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From toon at moene dot indiv dot nluug dot nl 2005-05-15 18:49 -------
Subject: Re: Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
corsepiu at gcc dot gnu dot org wrote:
> Joel, do you recall the target in RTEMS which has 4-byte floats only?
> (We recently had an issue with it floating point context sizes related to it?
> IIRC, it had been a powerpc variant and we were forced to drop it because GCC
> doesn't support it.
>
> BTW1: IFAIK, there also exist sh-variants (target tuple *-single*) which don't
> have 8byte floats. RTEMS doesn't support them, so I've never tried to build
> fortran for then.
Note that the major demand the Fortran Standard places on DOUBLE
PRECISION is that it takes up twice the amount of storage. It also is
supposed to be of "higher precision", but that is a QOI issue.
Cheers,
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203