Re: bitscan forward/reverse on Windows - Mailing list pgsql-hackers

From John Naylor
Subject Re: bitscan forward/reverse on Windows
Date
Msg-id CAFBsxsF3ye8UP6Xm2a42LuHsHj7d0scGHpu9FNhqBDbrG2MP9g@mail.gmail.com
Whole thread Raw
In response to Re: bitscan forward/reverse on Windows  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers


On Wed, Feb 8, 2023 at 3:14 PM John Naylor <john.naylor@enterprisedb.com> wrote:
> > 0001 adds asserts to the existing coding.
> > 0002 adds MSVC support. Tests pass on CI, but it's of course possible that there is some bug that prevents hitting the fastpath. I've mostly used the platform specific types, so some further cleanup might be needed.
>
> I've cleaned these up and verified on godbolt.org that they work as intended and still pass CI. I kept the Windows types as does other Winows code in the tree, but used bool instead of unsigned char because it's used like a boolean.
>
> 0003 is separate because I'm not quite sure how detailed to comment the #ifdef maze. Could be left out.
> 0004 simplifies AllocSetFreeIndex() in the course of supporting MSVC. The output is identical to HEAD in non-assert builds using gcc.
>
> 0002 through 0004 could be squashed together.
>
> This plugs a hole in our platform-specific intrinsic support and is fairly straightforward. Review welcome, but if there is none I intend to commit in a week or two.

I've committed 0001 separately, and squashed 0002 and 0004, deciding that 0003 didn't really add to readability.

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?
Next
From: Peter Eisentraut
Date:
Subject: Re: Allow tailoring of ICU locales with custom rules