Re: Allow non-wi wi

2017-10-06 Thread Mike Stump
> 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

Re: Allow non-wi wi

2017-10-06 Thread Richard Biener
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

Re: Allow non-wi wi

2017-10-06 Thread Richard Sandiford
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

Re: Allow non-wi wi

2017-10-05 Thread Richard Biener
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

Allow non-wi wi

2017-10-03 Thread Richard Sandiford
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