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

["corsepiu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>]

------- Additional Comments From corsepiu at gcc dot gnu dot org  2005-05-14 08:14 -------
(In reply to comment #17)
> 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.
> 
> 
> Also this is fortran requirement so technically it is not a design flaw 
> in gfortran but in the standard, I would complain to them instead of to 
> GCC about this. Yes we could circumvent this but that would be an extension.

Free free to hang on closely to standards ... to me, this sounds as being
stubborn and non-helpful to the fortran community, nor to GCC nor to embedded
systems. I'd prefer GCC to hang on to practical demands and implications
stemming from practice instead of being religious about standards ignoring
practical implications.

> And who  would be using fortran for embedded targets anyways.
Consider numerical applications on embedded systems using fortran libraries
(image processing, control applications etc.)

IMO, this is a hen-and-egg problem. Hardly anybody is using fortran on embedded
targets because the language is not available for many targets, and it is not
available for many targets, because the language is not able to support them/is
too non-portable.

In this particular case, I fail to understand why REAL8 must be available and I
fail to understand why this type can't be made conditionally available.

> g77 had the same issue until at least a 3.3 (or so) was released so having it
> not fixed for a long time which was about 4 releases after the first official
> GCC with g77 support (2.95).
Well, you know, gcc-4.0.0 is a major GCC release, gfortran is new ...
All this had caused me to have a look at known weeknesses in GCC.

The result (not limited to fortran) esp. wrt. embedded targets, is pretty
disillusioning.

-- 


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