This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: 2.95.3 segfault on simple syntactically correct input
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Karel Kulhavy <clock at atrey dot karlin dot mff dot cuni dot cz>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 13 Mar 2002 18:16:56 -0500
- Subject: Re: 2.95.3 segfault on simple syntactically correct input
A signal 11 usually means a hardware problem (memory) when you get it
inside gcc.
Thanks,
Andrew Pinski
On Wednesday, March 13, 2002, at 04:55 , Karel Kulhavy wrote:
> gcc: Internal compiler error: program cc1 got fatal signal 11
>
> Crashes on
> 2.95.3
> 2.95.4
>
> Doesn't crash on
> egcs-2.91.66
> 2.96
>
> You should spend less time on developping cutting-edge features and
> more time
> on ensuring the compiler at least doesn't crash on simple correct input.
>
> /* Run this command:
> * gcc -O2 segfault.c
> */
> unsigned char zero(unsigned char i)
> {
> return 0;
> }
>
> int main(int argc, char **argv)
> {
> unsigned char a;
>
> a=zero(a);
> a=zero(a);
> return 0;
> }
>
> --
> Karel 'Clock' Kulhavy
>