On 3/9/23 16:27, Lewis Hyatt via Gcc-patches wrote:
On Fri, Nov 04, 2022 at 10:03:13AM +0100, Jakub Jelinek via Gcc-patches wrote:Hi! The following pseudo-patch (for uname2c.h part just a pseudo patch with a lot of changes replaced with ... because it is too large but the important changes like -static const char uname2c_dict[59418] = +static const char uname2c_dict[59891] = -static const unsigned char uname2c_tree[208765] = { +static const unsigned char uname2c_tree[210697] = { are shown, full patch xz compressed will be posted separately due to mail limit) regenerates the libcpp tables with Unicode 15.0.0 which added 4489 new characters. As mentioned previously, this isn't just a matter of running the two libcpp/make*.cc programs on the new Unicode files, but one needs to manually update a table inside of makeuname2c.cc according to a table in Unicode text (which is partially reflected in the text files, but e.g. in Unicode 14.0.0 not 100% accurately, in 15.0.0 actually accurately). I've also added some randomly chosen subset of those 4489 new characters to a testcase. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?Hi Jakub- In addition to these files you updated last year for Unicode 15, we also need to update generated_cpp_wcwidth.h, which implements cpp_wcwidth() for diagnostics so we can output correct column numbers. There is a procedure outlined in the file contrib/unicode/README that accomplishes this. Is it OK to push the attached patch (gzipped since it is large and uninformative), which is the result of following the procedure? It went straightforwardly as expected, and bootstrap+regtest on x86-64 Linux is clean. Thanks!
Yes, please go ahead and push it. jeff
