On Tue, 19 Nov 2019, David Malcolm wrote: > If we're going with this approach, and redistributing those unicode data > files as part of our repo and tarballs, do we need some kind of > copyright/license statement that spells out the situation? What does > glibc do for this?
glibc includes the files in localedata/unicode-gen/ directory. My inclination is that we should include them in the GCC sources, but there were concerns about doing so when I asked about that issue when last updating the data used for warnings about normalization of UCNs in identifiers (which I should probably update again - given the work I did last time, this time it should just be a regeneration with newer input files) <https://gcc.gnu.org/ml/gcc-patches/2013-11/msg01932.html>. -- Joseph S. Myers jos...@codesourcery.com