On 8/1/19 2:49 AM, Richard Biener wrote:
On Wed, 31 Jul 2019, Martin Sebor wrote:
On 7/31/19 4:00 AM, Richard Biener wrote:
On Tue, 30 Jul 2019, Martin Sebor wrote:
On 7/30/19 9:19 AM, Jakub Jelinek wrote:
On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
Say something like thi
On Wed, 31 Jul 2019, Martin Sebor wrote:
> On 7/31/19 4:00 AM, Richard Biener wrote:
> > On Tue, 30 Jul 2019, Martin Sebor wrote:
> >
> > > On 7/30/19 9:19 AM, Jakub Jelinek wrote:
> > > > On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
> > > > > Say something like this POC:
> > > >
On 7/31/19 4:00 AM, Richard Biener wrote:
On Tue, 30 Jul 2019, Martin Sebor wrote:
On 7/30/19 9:19 AM, Jakub Jelinek wrote:
On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
Say something like this POC:
We have those already, see ctz_hwi, clz_hwi etc.
The thing is that BITMAP_WO
On Tue, 30 Jul 2019, Martin Sebor wrote:
> On 7/30/19 9:19 AM, Jakub Jelinek wrote:
> > On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
> > > Say something like this POC:
> >
> > We have those already, see ctz_hwi, clz_hwi etc.
> > The thing is that BITMAP_WORD isn't always the same
On 7/30/19 9:19 AM, Jakub Jelinek wrote:
On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
Say something like this POC:
We have those already, see ctz_hwi, clz_hwi etc.
The thing is that BITMAP_WORD isn't always the same type as unsigned
HOST_WIDE_INT, and so we need ones with the
On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
> Say something like this POC:
We have those already, see ctz_hwi, clz_hwi etc.
The thing is that BITMAP_WORD isn't always the same type as unsigned
HOST_WIDE_INT, and so we need ones with the BITMAP_WORD type.
Jakub
On 7/30/19 8:37 AM, Richard Biener wrote:
I've played with different BITMAP_WORD and BITMAP_ELEMENT_WORDS
values and found the code using CTZ and friends a bit unwieldly
to adjust. So I came up with a set of macros wrapping them
(_maybe_ inline overloads would be a cleaner solution, but ...).
