user/sven/glibc.git/libio, branch origin/master

libio: Properly link in function _IO_wfile_doallocate in static binaries

2026-03-10T16:24:17Z

This patch addresses Bug 33935 - _IO_wfile_doallocate not linked correctly when linking glibc statically. https://sourceware.org/bugzilla/show_bug.cgi?id=33935 The function _IO_wfile_doallocate has been added with pragma weak in vtable.c, while it is the only one symbol contained in wfiledoalloc.c, and has not been directly called in libio. In static binaries the true function symbol _IO_wfile_doallocate may not be correctly linked when linking glibc with cases contains wchar functions, but the weak symbol in vtable is linked instead, and cause segmentation fault when running. This patch fixes this with similar way to symbol _IO_file_doallocate, that add libio_static_fn_required(_IO_wfile_doallocate) in wgenops.c to make _IO_wfile_doallocate always link in static binaries. Reviewed-by: Adhemerval Zanella

libio: Fix deadlock between freopen, fflush (NULL) and fclose (bug 24963)

2026-02-23T13:19:38Z

The canonical lock ordering for stream list processing is locking list_all_lock first, then individual streams as needed. The fclose implementation reversed that, and the freopen implementation performed list operations under the reverse order, too. Unlinking in fclose was already unconditional, and the early unlinking looks unnecessary: _IO_file_close_it would call it even for !_IO_IS_FILEBUF streams. There is still a remaining concurrency defect because _IO_new_file_init_internal links in the stream before it is fully initialized, and it is not locked at this point. Reviewed-by: Arjun Shankar

Update copyright dates with scripts/update-copyrights

2026-01-01T21:42:29Z

Handle clang -Wignored-attributes on weak aliases

2025-12-09T11:58:10Z

Clang issues a warning for double alias redirection, indicating that thei original symbol is used even if a weak definition attempts to override it. For instance, in the construction: int __internal_impl (...) {} weak_alias (__internal_impl, external_impl); #if SOMETHING weak_alias (external_impl, another_external_impl) #endif Clang warns that another_external_impl always resolves to __internal_impl, even if external_impl is a weak reference. Using the internal symbol for both aliases resolves this warning. This issue also occurs with certain libc_hidden_def usage: int __internal_impl (...) {} weak_alias (__internal_impl, __internal_alias) libc_hidden_weak (__internal_alias) In this case, using a strong_alias is sufficient to avoid the warning (since the alias is internal, there is no need to use a weak alias). However, for the constructions like: int __internal_impl (...) {} weak_alias (__internal_impl, __internal_alias) libc_hidden_def (__internal_alias) weak_alias (__internal_impl, external_alias) libc_hidden_def (external_alias) Clang warns that the internal external_alias will always resolve to __GI___internal_impl, even if a weak definition of __GI_internal_impl is overridden. For this case, a new macro named static_weak_alias is used to create a strong alias for SHARED, or a weak_alias otherwise. With these changes, there is no need to check and enable the -Wno-ignored-attributes suppression when using clang. Checked with a build on affected ABIs, and a full check on aarch64, armhf, i686, and x86_64. Reviewed-by: Sam James

libio: null terminate the buffer upon initial allocation in getdelim

2025-12-06T04:09:36Z

Commit 33eff78c8b28adc4963987880e10d96761f2a167 caused issues in nbdkit which had code similar to this to get the last line of the file: while (getline (&line, &len, fp) != -1) ; /* Process LINE. */ After that commit, line[0] would be equal to '\0' instead of containing the last line of the file like before that commit. A recent POSIX issue clarified that the behavior before and after that commit are allowed, since the contents of LINE are unspecified after -1 is returned [1]. However, some programs rely on the previous behavior. This patch null terminates the buffer upon getdelim/getline's initial allocation. This is compatible with previous glibc versions, while also protecting the caller from reading uninitialized memory if the file is empty, as long as getline/getdelim does the initial allocation. [1] https://www.austingroupbugs.net/bug_view_page.php?bug_id=1953 Suggested-by: Eric Blake Reviewed-by: Eric Blake

strops: use strlen instead of strchr for string length

2025-12-01T15:42:54Z

For wide string the equivalent funtion __wcslen is used. This change makes it more symetrical. Reviewed-by: Florian Weimer

Define C23 header version macros

2025-11-27T19:32:49Z

C23 defines library macros __STDC_VERSION_

_H__ to indicate that a header has support for new / changed features from C23. Now that all the required library features are implemented in glibc, define these macros. I'm not sure this is sufficiently much of a user-visible feature to be worth a mention in NEWS. Tested for x86_64. There are various optional C23 features we don't yet have, of which I might look at the Annex H ones (floating-point encoding conversion functions and _Float16 functions) next. * Optional time bases TIME_MONOTONIC, TIME_ACTIVE, TIME_THREAD_ACTIVE. See - we need to review / update that patch. (I think patch 2/2, inventing new names for all the nonstandard CLOCK_* supported by the Linux kernel, is rather more dubious.) * Updating conform/ tests for C23. * Defining the rounding mode macro FE_TONEARESTFROMZERO for RISC-V (as far as I know, the only architecture supported by glibc that has hardware support for this rounding mode for binary floating point) and supporting it throughout glibc and its tests (especially the string/numeric conversions in both directions that explicitly handle each possible rounding mode, and various tests that do likewise). * Annex H floating-point encoding conversion functions. (It's not entirely clear which are optional even given support for Annex H; there's some wording applied inconsistently about only being required when non-arithmetic interchange formats are supported; see the comments I raised on the WG14 reflector on 23 Oct 2025.) * _Float16 functions (and other header and testcase support for this type). * Decimal floating-point support. * Fully supporting __int128 and unsigned __int128 as integer types wider than intmax_t, as permitted by C23. Would need doing in coordination with GCC, see GCC bug 113887 for more discussion of what's involved.

Enable --enable-fortify-source with clang

2025-11-21T16:13:11Z

clang generates internal calls for some _chk symbol, so add internal aliases for them, and stub some with rtld-stubbed-symbols to avoid ld.so linker issues. Reviewed-by: Sam James

libio: Add terminating NUL when the first character is EOF in getdelim [BZ #28038]

2025-10-10T00:38:01Z

POSIX requires that the buffer used by getdelim/getline add a terminating NUL whenever an EOF is read. * libio/iogetdelim.c (__getdelim): Add a NUL byte when the first __underflow is called. * libio/tst-getdelim.c (do_test): Add a test case for the bug. Reviewed-by: Florian Weimer

libio: Define AT_RENAME_* with the same tokens as Linux

2025-09-05T17:02:59Z

Linux uses different expressions for the RENAME_* and AT_RENAME_* constants. Mirror that in , so that the macro redefinitions do not result in preprocessor warnings. Reviewed-by: Collin Funk