🚀 go-pugleaf

Compiling the next code (fatal.c):

    main()
    {
        void *test(void)
        {
            printf("test\n");
                return test;       
        }
        void *test(void);
    }

gives:

    cc: Internal compiler error: program cc1 got fatal signal 11

apperently suggesting either a hardware-fault or a compiler bug
(segmentation fault).
I know that this code is incorrect, it doesn't matter.
A reliable compiler should never crash, anyway.
Testing this code on another Linux computer shows that is probably
not a hardware problem.

A gcc-compiler (2.5.3) on the HP/UX platform did also exit with 
fatal signal:

    fatal.c: In function `main':
    fatal.c:10: internal error--unrecognizable insn:
    (insn 28 26 29 (set (reg:SI 109)
            (nil)) -1 (nil)
        (nil))
    gcc: Internal compiler error: program cc1 got fatal signal 6

This makes me conclude that it is a compiler bug.
I could not find anything about it in the existing bug-lists.

general information:
Linux kernel 1.2.13
gcc version 2.7.0
libraries upgraded to 4.7.2

HP/UX version ??
gcc version 2.5.3
libraries ??

regards,
--
Ferdinand de Bouvere
<bouvere@nikhefk.nikhef.nl>
<ferdinan@htsa.hva.nl>