Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version
Nawww... I've tried this on a bunch of different machines.. as a matter
of fact it replicates with gcc version 2.7.2.1 from December of last
year. I find it hard to believe that I have 80 machines that all
exhibit the exact same memory failure... :-)
-John
Yep - others have
On Mon, 20 Dec 1999, Thomas David Rivers wrote:
! FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
! cc: Internal compiler error: program cc1 got fatal signal 11
!
!
!
! static void getsig11(parfree,dbl,lambda)
! long parfree;
! double *dbl;
! double *lambda;
! {
! long i, j;
! j = -1;