Re: Bug in fortran compiler on Alpha

Re: Bug in fortran compiler on Alpha

[Toon Moene]

>        subroutine rpoly()
>        real a,b,c
>        a=amin1(b,c)
>        end

>  f77 -v Reading specs from
>  /usr/lib/gcc-lib/alpha-redhat-linux/egcs-2.90.27/specs
>  gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)

>  f77 -mieee-with-inexact  -c  rpoly.f rpoly.f: In
>  subroutine `rpoly':  rpoly.f:4: internal
>  error--unrecognizable insn:  (insn 12 11 13 (set (reg:DF
>  71)
>  	(lt:DF (float_extend:DF (reg:SF 69))
>  	    (float_extend:DF (reg:SF 70)))) -1 (nil)
>      (nil)) f77: Internal compiler error: program f771
>  got fatal signal 6

I am fairly sure this bug is fixed in the current release  
(egcs-1.1); see http://egcs.cygnus.com for information how to obtain  
it.

Unfortunately, I cannot readily test this hypothesis, as I do not  
have a 1.1 version lying around on the Alpha I've access to.

Hope this helps,
Toon.

Re: Bug in fortran compiler on Alpha

[Craig Burley]

>f77 -v
>Reading specs from /usr/lib/gcc-lib/alpha-redhat-linux/egcs-2.90.27/specs
>gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)

egcs 1.1 was recently released, and might well fix the problem you're
running into.

(BTW, it does look like you're running g77 indeed.  egcs 1.0.x are
the only versions that don't report a ton of info for `f77 -v' or
`g77 -v', which throws some long-time g77 users off a bit; egcs 1.1
restores this behavior.)

        tq vm, (burley)

Re: Bug in fortran compiler on Alpha

[N8TM]

In a message dated 9/16/98 10:32:52 AM Pacific Daylight Time,
scilab@velo.inria.fr writes:

>      subroutine rpoly()
>        real a,b,c
>        a=amin1(b,c)
>        end
>  
>  f77 -v
>  Reading specs from /usr/lib/gcc-lib/alpha-redhat-linux/egcs-2.90.27/specs
>  gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)
>  
>  f77 -mieee-with-inexact  -c  rpoly.f

Why not use g77? For error messages to make any sense when using intermediate
C code, you should examine and report that C code.  Current versions of g77
don't give me any error indications with this nonsense do-nothing code.