Re: Found gcc bug while trying to correct another one

[Jeffrey A Law <law at cygnus dot com>]

  In message <199806051335.PAA28713@keksy.mchp.siemens.de>you write:
  > int main(int argc,const char *argv[])
  > {
  >  int i;
  >  for(i=3;i<10;i++);
  >  if(i==10) 
  >      puts("OK");
  >  else
  >      printf("not ok: %d != 10\n",i);
  >  return 0;
  > }
This was fixed in the development sources within the last few days.

  > I got a segmentation Fault during the make step of gcc
  > (Signal 11) in 
  > /home/kahlert/LOCAL/obj/gcc/xgcc 
  >   -B/home/kahlert/LOCAL/obj/gcc/  -DIN_GCC   -DUSE_GNULIBC_1 
  >   -g -O2 -I./include  -I. -I/home/kahlert/LOCAL/egcs-19980531/gcc 
  >   -I/home/kahlert/LOCAL/egcs-19980531/gcc/config \ 
  >   -c /home/kahlert/LOCAL/egcs-19980531/gcc/objc/hash.c -o objc/hash.o
  > with the final output
  > 136451592 : 1
  > 140 : xgcc: Internal compiler error: program cc1 got fatal signal 11
  > 
  > So somebody seems to overwrite the next-field in the biv at 
  > address 136451592 with 140. 
  > This looks like a further gcc bug to me, 
  > which hasn't anything to do with my bug.
Don't know about this one.  Of course you haven't told us anythign
about your target system, so it's hard to debug what might be
happening with this problem.

jeff

ps.  egcs-bugs is the right list for this discussion, not egcs.