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: "corsepiu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 May 2005 08:33:58 -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 corsepiu at gcc dot gnu dot org 2005-05-14 08:33 -------
(In reply to comment #16)
> Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
>
>
> On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
>
> > * f95 disqualifies ifselves from several embedded targets, if it can
> > not be
> > built/used on targets not supporting REAL8. IIRC, there even exist
> > variants of
> > major _targets_ (IIRC, powerpc, m68k) which do not support REAL8.
> > IMO, this is a design flaw, which should be in your interest to be
> > circumvented.
>
> Huh, PPC soft float supports REAL 8 still.
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.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |joel at oarcorp dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203