[Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90

["joel at oarcorp dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From joel at oarcorp dot com  2005-05-16 14:00 -------
Subject: Re:  Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90

corsepiu at gcc dot gnu dot org wrote:
> ------- 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.

I don't know of any specific models.  The code in RTEMS was based upon 
an early (mid-90's) version of the PowerPC Programming Environments 
Manual.  I recall that version of the manual as being clear that a 
single precision PowerPC was possible within the architectural definition.

I just downloaded the current one from FreeScale and I see no hint that
this architectural option is allowed anymore.

> 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.

--joel


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203