This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


------- Additional Comments From corsepiu at gcc dot gnu dot org  2005-05-16 14:05 -------
(In reply to comment #24)
> 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?
I've found it. The RTEMS sources claim the "PowerPC 602" to have 4byte floats,
only. 

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

Cf. gcc-4.0-branch/fortran/trans-types.c ca. line 228ff:

      /* F95 14.6.3.1: A nonpointer scalar object of type double precision
         real ... occupies two contiguous numeric storage units.
...
                          .. But at present there are
         no GCC targets for which a two-word type does not exist, so we
         just let gfc_validate_kind abort and tell us if something breaks.  */

Well, the h8300 has 8byte types (seemingly long long), but it doesn't have 8byte
floats. As the comment is on REAL8, ... there is something fishy in there.

-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]