Re: Hide exposed impl detail of wchar.c
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jubilee Young <workingjubilee@gmail.com>, pgsql-hackers@lists.postgresql.org, John Naylor <johncnaylorls@gmail.com>
Date: 2023-11-17T04:38:22Z
Lists: pgsql-hackers
On Thu, Nov 16, 2023 at 06:06:30PM -0500, Tom Lane wrote: > I'm generally sympathetic to the idea that simd.h was a rather large > dependency to add to something as widely used as pg_wchar.h. So I'd > favor getting it out of there just on compilation-time grounds, > independently of whether it's causing active problems. That argument > wouldn't justify a back-patch, but "it's causing problems" might. Given the lack of evidence of anyone else using is_valid_ascii(), I'm leaning towards back-patching being the better option in this case. I don't know if it'll be feasible to keep simd.h out of all headers that third-party code might want to use forever, but that's not an argument against doing this right now for pgrx. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
Move is_valid_ascii() to ascii.h.
- 3726c1cb0e3b 15.6 landed
- 1b924a86e696 16.2 landed
- 97287bdfae41 17.0 landed
-
Use SSE2 in is_valid_ascii() where available.
- 121d2d3d70ec 16.0 cited