> On Oct 6, 2017, at 2:35 AM, Richard Sandiford
> wrote:
>
> Richard Biener writes:
>> On Tue, Oct 3, 2017 at 8:34 PM, Richard Sandiford
>> wrote:
>>> This patch uses global rather than member operators for wide-int.h,
>>> so that the first operand can be a non-wide-int type.
>>
>> Not sure
On Fri, Oct 6, 2017 at 11:35 AM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Tue, Oct 3, 2017 at 8:34 PM, Richard Sandiford
>> wrote:
>>> This patch uses global rather than member operators for wide-int.h,
>>> so that the first operand can be a non-wide-int type.
>>
>> Not sure why w
Richard Biener writes:
> On Tue, Oct 3, 2017 at 8:34 PM, Richard Sandiford
> wrote:
>> This patch uses global rather than member operators for wide-int.h,
>> so that the first operand can be a non-wide-int type.
>
> Not sure why we had the in-class ones. If we had some good arguments
> they'd st
On Tue, Oct 3, 2017 at 8:34 PM, Richard Sandiford
wrote:
> This patch uses global rather than member operators for wide-int.h,
> so that the first operand can be a non-wide-int type.
Not sure why we had the in-class ones. If we had some good arguments
they'd still stand. Do you remember?
> The
This patch uses global rather than member operators for wide-int.h,
so that the first operand can be a non-wide-int type.
The patch also removes the and_not and or_not member functions.
It was already inconsistent to have member functions for these
two operations (one of which was never used) and