aboutsummaryrefslogtreecommitdiff
path: root/libio/tst-fgetws.c
diff options
context:
space:
mode:
authorAndreas Schwab <schwab@suse.de>2023-10-08 18:23:30 +0200
committerAndreas Schwab <schwab@suse.de>2023-10-16 09:59:32 +0200
commit5aa1ddfcb3374425b7fe9a1389b98a45a47e4a77 (patch)
tree2270c4d4c0926cc2358e7bf249d44d001ceda397 /libio/tst-fgetws.c
parent4a829d70ab3bc9e69f3d186471d043e07e0d78d8 (diff)
downloadglibc-5aa1ddfcb3374425b7fe9a1389b98a45a47e4a77.tar
glibc-5aa1ddfcb3374425b7fe9a1389b98a45a47e4a77.tar.gz
glibc-5aa1ddfcb3374425b7fe9a1389b98a45a47e4a77.tar.bz2
glibc-5aa1ddfcb3374425b7fe9a1389b98a45a47e4a77.zip
Avoid maybe-uninitialized warning in __kernel_rem_pio2
With GCC 14 on 32-bit x86 the compiler emits a maybe-uninitialized warning: ../sysdeps/ieee754/dbl-64/k_rem_pio2.c: In function '__kernel_rem_pio2': ../sysdeps/ieee754/dbl-64/k_rem_pio2.c:364:20: error: 'fq' may be used uninitialized [-Werror=maybe-uninitialized] 364 | y[0] = fq[0]; y[1] = fq[1]; y[2] = fw; | ~~^~~ This is similar to the warning that is suppressed in the other branch of the switch. Help the compiler knowing that the variable is always initialized, which also makes the suppression obsolete.
Diffstat (limited to 'libio/tst-fgetws.c')
0 files changed, 0 insertions, 0 deletions