f771 assertion failure

Craig Burley burley@gnu.ai.mit.edu
Sat Sep 27 22:24:00 GMT 1997


>> ../egcs/gcc/f/bad.c:337: failed assertion `ffebad_index_ != FFEBAD_MAX_'
>> gcc: Internal compiler error: program f771 got fatal signal 6
>
>This while compiling apsi.f from spec95's 145.fpppp.  Anyone know
>what it means and where to look?  I have several other ocurrences
>to for those who have spec95...

Presumably something's wrong in the compiler.  See who's calling
ffebad_string(), which is where the abort happens -- probably
someone is calling ffebad_string() once too often, which could
happen if an earlier ffebad_start() call was made without a
subsequent ffebad_finish() call.

>Also, I get several of these
>
>> apsi.f: In subroutine `rffti1':
>> apsi.f:4886: warning:
>>          CALL RFFTI1 (N,WSAVE(N+1),WSAVE(2*N+1))
>>               1
>> apsi.f:4983: (continued):
>>          SUBROUTINE RFFTI1 (N,WA,IFAC)
>>                     2
>> Argument #3 (named `ifac') of `rffti1' is one type at (2) but is \
>> some other type at (1) [info -f g77 M GLOBALS]
>
>but don't know enough about Fortran to know what the implications
>are.  What actually happens?  The subroutine gets fed bad data? 
>Something similar to c++'s non-const-reference, which gets fed
>the address of a temporary?

Have you tried "info -f g77 M GLOBALS"?  It *should* answer these
questions -- let us know if it doesn't.

        tq vm, (burley)



More information about the Gcc mailing list