[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: clang memory sanitizer report unsigned int overflow
- From: bil til <biltil52@...>
- Date: Sat, 7 Jan 2023 08:14:12 +0100
Am Sa., 7. Jan. 2023 um 08:06 Uhr schrieb Mouse <mouse@rodents-montreal.org>:
> Actually, practically every Linux system live today has (some)
> characters larger than 8 bits; they have variable-size characters,
> since they use UTF-8. (Indeed, I find it depressingly difficult to
> make them use single-byte character sets like 8859-*.)
... you have to distinguish between "CPU core registers" and "string
constructs".
A CPU core based on UTF-8 would be a "crazy construct" full of
cumbersomeness and exceptions :).
For strings as used in Internet (and everywhere, were multiple
language writing styles are used), UTF-8 is a very ingenious and "not
to think away" coding type... . (it was a main problem / error
decision of Microsoft in the 1990 to go with "fix 16-bit Unicode" for
windows instead of flexible UTF8 - only now in Win10 MS corrected this
and at least now allows Win10 to use UTF8 in operating system support
style...).
- References:
- clang memory sanitizer report unsigned int overflow, Jo Ember
- Re: clang memory sanitizer report unsigned int overflow, David Sicilia
- Re: clang memory sanitizer report unsigned int overflow, Roberto Ierusalimschy
- Re: clang memory sanitizer report unsigned int overflow, Lorenzo Donati
- Re: clang memory sanitizer report unsigned int overflow, bil til
- Re: clang memory sanitizer report unsigned int overflow, Lorenzo Donati
- Re: clang memory sanitizer report unsigned int overflow, Lorenzo Donati
- Re: clang memory sanitizer report unsigned int overflow, bil til
- Re: clang memory sanitizer report unsigned int overflow, Sean Conner
- Re: clang memory sanitizer report unsigned int overflow, Mouse