Hello,
Thanks for your response.
Bruno Haible wrote:
> Regarding the Default_Ignorable_Code_Point characters: Making all of
> them
> non-spacing would assign width 0 to the characters
> U+115F HANGUL CHOSEONG FILLER
> U+3164 HANGUL FILLER
> U+FFA0 HALFWIDTH HANGUL FILLER
> But this does not
On 2024-02-11 04:46, Bruno Haible wrote:
The first question is how to include tzdata in gnulib.
- AFAICS, the main data file (without comments) is tzdata.zi and is about
100 KB large. It can be upgraded simply by copying the newest tzdata.zi
from a newer tzdata distribution. Includin
Hi,
Jules Bertholet wrote:
> Makes two changes to the set of characters considered nonspacing:
>
> - Makes `Prepended_Concatenation_Mark`s no longer nonspacing.
> This matches the Unicode spec (which specifies these as taking up space
> in front of the characters they modify), and also aligns
When upgrading to Unicode 9.0.0, it was forgotten to add a new character
property, that was introduced in Unicode 9.0.0. This patch adds it now.
2024-02-12 Bruno Haible
Implement a new property, added by Unicode 9.0.0.
* lib/gen-uni-tables.c (is_property_prepended_concatenatio
Collin Funk wrote:
> Both ISO C 23 § 5.2.4.2.1 and
> Annex E seem to say BOOL_WIDTH must be exactly 1.
I have no idea what the footnote "This value is exact." in § 5.2.4.2.1 means.
And Annex E is informational, not normative.
Therefore, I think, the grounds for claiming a clang bug are weak.
Bru
On 2/12/24 5:09 AM, Bruno Haible wrote:
> BOOL_WIDTH = 1, BOOL_MAX = 1
> with CC="gcc -std=gnu2x", but
> BOOL_WIDTH = 8, BOOL_MAX = 1
> with CC="clang -std=gnu2x" (for all clang version 14 ... 17).
Same results with GCC 14 and Clang 19.
> Apparently I had misinterpreted the meaning of BOOL_
Oops, there was still a reference to this module.
2024-02-12 Bruno Haible
posixtm tests: Fix reference to undefined module (regr. 2024-02-09).
* modules/posixtm-tests (Depends-on): Remove strftime. Add
strftime-fixes.
diff --git a/modules/posixtm-tests b/modules/posix
With clang 17 and CC="clang -std=gnu2x", I see this compilation error:
../../gltests/test-limits-h.c:118:16: error: static assertion failed due to
requirement '1 == (((1U << (8 - 1)) - 1) * 2) + 1'
118 | static_assert (BOOL_MAX == (((1U << (BOOL_WIDTH - 1)) - 1) * 2) + 1);
|
The configure test
checking for alignas and alignof...
reports 'yes, macros' with gcc, but 'no' with
clang 17 and CC="clang -std=gnu2x". In my opinion, this is a clang bug.
This patch documents it.
2024-02-12 Bruno Haible
stdalign: Document a clang 17 bug.
* doc/posix-heade
On a glibc system, with clang 17 and CC="clang -std=gnu2x", the configure test
checking whether getcwd (NULL, 0) allocates memory for result...
reports 'no' instead of 'yes'. This is because of this compilation error:
conftest.c:169:16: error: conflicting types for 'getcwd'
169 |
Hi Florian,
Florian Weimer wrote:
> Without this change, these probes fail unconditionally with GCC 14
> because they do not use the correct argument types.
Thanks for noticing and reporting it! Applied.
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=f5b70b135a355d7f957ddd8119a8
Without this change, these probes fail unconditionally with GCC 14
because they do not use the correct argument types.
---
m4/pthread-spin.m4| 2 +-
m4/pthread_mutex_timedlock.m4 | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/m4/pthread-spin.m4 b/m4/pthread-spi
12 matches
Mail list logo
