public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "smcv at collabora dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug locale/31030] ERA segments are nul-separated rather than semicolon-separated Date: Mon, 15 Jan 2024 13:23:30 +0000 [thread overview] Message-ID: <bug-31030-131-KiAMsCgM2H@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31030-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31030 Simon McVittie <smcv at collabora dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smcv at collabora dot com --- Comment #2 from Simon McVittie <smcv at collabora dot com> --- GLib currently uses (intptr_t) nl_langinfo(_NL_TIME_ERA_NUM_ENTRIES) in its workaround for the ERA not being as documented, but it seems that there is a separate problem with that on 64-bit big-endian architectures: https://gitlab.gnome.org/GNOME/glib/-/issues/3225 On x86_64, in the Japanese (ja_JP.utf8) locale, (intptr_t) nl_langinfo(_NL_TIME_ERA_NUM_ENTRIES) is 0x0000'0000'0000'000b (decimal 11) which seems to be what is expected. But on s390x, the result I see is 0x0000'000b'0000'0000 (a very large number): it looks as though the two 32-bit words have been swapped? There is a test program attached to the GLib issue which might be useful. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-15 13:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-03 17:17 [Bug locale/31030] New: " bugzilla at tecnocode dot co.uk 2023-12-05 14:15 ` [Bug locale/31030] " schwab@linux-m68k.org 2024-01-15 13:23 ` smcv at collabora dot com [this message] 2024-01-15 13:31 ` smcv at collabora dot com 2024-01-15 13:34 ` schwab@linux-m68k.org 2024-01-15 13:35 ` schwab@linux-m68k.org 2024-01-15 13:50 ` bugzilla at tecnocode dot co.uk 2024-01-16 21:58 ` aurelien at aurel32 dot net
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31030-131-KiAMsCgM2H@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).