On Wed, Mar 4, 2020 at 1:26 AM Martin Sebor wrote:
>
> On 3/3/20 11:50 AM, Richard Biener wrote:
> > On March 3, 2020 4:39:34 PM GMT+01:00, Martin Sebor
> > wrote:
> >> On 3/3/20 2:42 AM, Richard Biener wrote:
> >>> On Tue, Mar 3, 2020 at 12:04 AM Martin Sebor
> >> wrote:
>
> The wide
On 3/3/20 11:50 AM, Richard Biener wrote:
On March 3, 2020 4:39:34 PM GMT+01:00, Martin Sebor wrote:
On 3/3/20 2:42 AM, Richard Biener wrote:
On Tue, Mar 3, 2020 at 12:04 AM Martin Sebor
wrote:
The wide_int APIs expect operands to have the same precision and
abort when they don't. This is
On March 3, 2020 4:39:34 PM GMT+01:00, Martin Sebor wrote:
>On 3/3/20 2:42 AM, Richard Biener wrote:
>> On Tue, Mar 3, 2020 at 12:04 AM Martin Sebor
>wrote:
>>>
>>> The wide_int APIs expect operands to have the same precision and
>>> abort when they don't. This is especially insidious in code wh
On 3/3/20 2:42 AM, Richard Biener wrote:
On Tue, Mar 3, 2020 at 12:04 AM Martin Sebor wrote:
The wide_int APIs expect operands to have the same precision and
abort when they don't. This is especially insidious in code where
the operands normally do have the same precision but where mixed
prec
On Tue, Mar 3, 2020 at 12:04 AM Martin Sebor wrote:
>
> The wide_int APIs expect operands to have the same precision and
> abort when they don't. This is especially insidious in code where
> the operands normally do have the same precision but where mixed
> precision arguments can come up as a re
The wide_int APIs expect operands to have the same precision and
abort when they don't. This is especially insidious in code where
the operands normally do have the same precision but where mixed
precision arguments can come up as a result of unusual combinations
optimization options. That is al
