diff options
| author | John Naylor <john.naylor@postgresql.org> | 2023-07-31 13:34:29 +0700 |
|---|---|---|
| committer | John Naylor <john.naylor@postgresql.org> | 2023-07-31 14:46:21 +0700 |
| commit | 39055cb4ccd5b521ceb802b6a8194de912a422cc (patch) | |
| tree | 6ba2bab47e7c822c20618e5bc1e6b9be485443bb /src/interfaces | |
| parent | 7395a90db87bcb2f617d3c486657813122d3f151 (diff) | |
| download | postgresql-39055cb4ccd5b521ceb802b6a8194de912a422cc.tar.gz postgresql-39055cb4ccd5b521ceb802b6a8194de912a422cc.zip | |
Bring some MSVC asserts in line with other platforms
MSVC's _BitScan* functions return a boolean indicating whether any
bits were set in the input, and we were previously asserting that
they returned true, per our API. This is correct. However, other
platforms simply assert that the input is non-zero, so do that to be
more consistent.
Noted while investigating a hypothesis from Ranier Vilela about
undefined behavior, but this is not his proposed patch.
Discussion: https://www.postgresql.org/message-id/CAEudQAoDhUZyKGJ1vbMGcgVUOcsixe-%3DjcVaDWarqkUg163D2w%40mail.gmail.com
Diffstat (limited to 'src/interfaces')
0 files changed, 0 insertions, 0 deletions