On 8/7/12, Mike Stump <mikest...@comcast.net> wrote: > On Aug 7, 2012, at 11:42 AM, Lawrence Crowl wrote: > > On 8/7/12, Mike Stump <mikest...@comcast.net> wrote: > > > On Aug 6, 2012, at 5:35 PM, Lawrence Crowl wrote: > > > > Convert double_int from a struct with function into a class > > > > with operators and methods. > > > > > > We have a wide_int class that replaces this class. :-( > > > > Really? Where? I don't see neither definition nor use > > under gcc. > > It is being developed; it is largely done, but is going through > final reviews now. When we finish with those review bits, we'll > send it out. It sounds like you'll beat us to the merge window, > so, we'll cope with the fallout.
Can I have a pointer to the interface? > > > It would have been better to just convert it. > > > > That depends on how easy it is to migrate. In the process I > > learned that double_int isn't actually a double int, but is a > > precision-controlled int. > > Well, I'd call it a pair of HOST_WIDE_INTs... I think calling > it a precision-controlled int is a tad optimistic. For example, > if want to control it to be 2048 bits, you'd find that your hopes > are misplaced. :-) Yes, well, it's clearly all relying on the host being bigger than the target. -- Lawrence Crowl
