flow patch for building ia64

[amacleod@cygnus.com]

>> So... there are 2 solutions. Since this doesn't seem to be 
>> affecting anything except ia64, the simple thing is to 
>> not mark the return_address_register as call-killed. b0 is
>> marked, so I dont think this will have any undesired side effects.
>> 
>> The other option would be to look at the register generated by the 
>> call to gen_rtx_REG and test whether it is call clobbered or not. 
>> This seem like a more general solution, but I dont know if that
>> might have other unexpected side effects....  Either one
>> solves the problem for ia64.


uhhh. ok bootstrap fails, but it *looks* independant of this. Both
fail at the same point early in stage 2,

stage1/xgcc -Bstage1/ -B/install/egcs0717/ia64-unknown-linux/bin/ -c  -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I. -I/src/egcs0717/egcs/gcc -I/src/egcs0717/egcs/gcc/. -I/src/egcs0717/egcs/gcc/config -I/src/egcs0717/egcs/gcc/../include /src/egcs0717/egcs/gcc/gengenrtl.c
/src/egcs0717/egcs/gcc/gengenrtl.c: In function `gendecl':
/src/egcs0717/egcs/gcc/gengenrtl.c:266: Internal compiler error in propagate_one_insn, at flow.c:4986
Please submit a full bug report,
with preprocessed source if appropriate.


Same function, but this time its not a prologue/epilgue instruction
directly... its a copy of ar.pfs to a register and a usage in 
a sibcall epilogue...  same code area though.
  I'll take a look at it tomorrow.

Andrew