On Fri, Oct 5, 2012 at 3:18 PM, Richard Sandiford <rdsandif...@googlemail.com> wrote: > Richard Sandiford <rdsandif...@googlemail.com> writes: >>>>> How is CONST_WIDE_INT variable size? >>>> >>>> It's just the usual trailing variable-length array thing. >>> >>> Good. Do you get rid of CONST_DOUBLE (for integers) at the same time? >> >> Yeah. I initially thought it might be OK to keep them and have >> CONST_INT, integer CONST_DOUBLEs and CONST_WIDE_INT alongside >> each other. (The way the patch is structured means that the >> choice of whether to keep integer CONST_DOUBLEs can be changed >> very easily.) But Kenny convinced me it was a bad idea. > > Sorry to follow up on myself, but to clarify: I was talking about > converted targets here. (As in, I originally thought even converted > targets could continue to use integer CONST_DOUBLEs.) > > Unconverted targets continue to use CONST_DOUBLE.
Why is it that not all targets are "converted"? What's the difficulty with that? I really do not like partially transitioning there. Richard. > Richard