Re: Cost of having an immediate use in the phi argument

2005-09-18 Thread Daniel Berlin
On Sun, 2005-09-18 at 09:13 -0400, Andrew MacLeod wrote: > On Sat, 2005-09-17 at 14:59, Daniel Berlin wrote: > > It seems the only reason we have PHI_ARG_IMM_USE_NODE (and a struct > > ssa_use_operand_d) in a phi node argument (struct phi_arg_d) is *just* > > so we can iterate over the uses and han

Re: Cost of having an immediate use in the phi argument

2005-09-18 Thread Andrew MacLeod
On Sat, 2005-09-17 at 14:59, Daniel Berlin wrote: > It seems the only reason we have PHI_ARG_IMM_USE_NODE (and a struct > ssa_use_operand_d) in a phi node argument (struct phi_arg_d) is *just* > so we can iterate over the uses and hand back use_operand_p. > > I'm talking, in particular, about: >

Cost of having an immediate use in the phi argument

2005-09-17 Thread Daniel Berlin
It seems the only reason we have PHI_ARG_IMM_USE_NODE (and a struct ssa_use_operand_d) in a phi node argument (struct phi_arg_d) is *just* so we can iterate over the uses and hand back use_operand_p. I'm talking, in particular, about: struct phi_arg_d GTY(()) { /* imm_use MUST be the first el