Re: fortran/9793: Internal compiler error in `float_signal', at toplev.c:2442

Re: fortran/9793: Internal compiler error in `float_signal', at toplev.c:2442

[ljrittle]

Synopsis: Internal compiler error in `float_signal', at toplev.c:2442

State-Changed-From-To: analyzed->closed
State-Changed-By: ljrittle
State-Changed-When: Fri Mar 28 04:31:00 2003
State-Changed-Why:
    Confirmed fixed in target environment on mainline and 3.3 branch.  Thanks for the PR.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9793

Re: fortran/9793: Internal compiler error in `float_signal', at toplev.c:2442

[bangerth]

Synopsis: Internal compiler error in `float_signal', at toplev.c:2442

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Feb 21 21:47:54 2003
State-Changed-Why:
    Confirmed. Still exists in 3.2.2, 3.3 and 3.4. Surprisingly
    simple to trip gcc, he? :-)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9793

fortran/9793: Internal compiler error in `float_signal', at toplev.c:2442

[larson]

>Number:         9793
>Category:       fortran
>Synopsis:       Internal compiler error in `float_signal', at toplev.c:2442
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 21 21:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     larson@w6yx.stanford.edu
>Release:        F77 version 2.95.4 20020320 [FreeBSD]
>Organization:
>Environment:

>Description:
The simple program:

        integer a, b, c
 
        c = -2147483648 / -1
 
        a = 1
        b = 0
        c = a / b
 
        print *, c
 
        end

gets this error:

foo.f: In program `MAIN__':
foo.f:5: Internal compiler error in `float_signal', at toplev.c:2442
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.


Obviously, it attempted to evaluate a constant expression
that it couldn't do.  Interestingly, it got the line number
wrong, as the error was not on source line 5 (it was really
on line 3).

This was compiling with  f77 -g -o foo foo.f

>How-To-Repeat:
attempt to compile with given flags.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: