https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115827
Bug ID: 115827
Summary: uninit-17.c no longer emits expected warning on
arm-none-eabi
Product: gcc
Version: 13.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: azoff at gcc dot gnu.org
Target Milestone: ---
When running tests on arm-gnu-toolchain-13.3.rel1-x86_64-arm-none-eabi, I see
the following failures in the log:
FAIL: gcc.dg/auto-init-uninit-17.c unconditional (test for warnings, line 14)
FAIL: gcc.dg/uninit-17.c unconditional (test for warnings, line 14)
Both of these errors comes from that the compiler no longer emits the expected
warning after basepoints/gcc-13-1762-gf9d4c3b45c5.
With basepoints/gcc-13-1761-g68871a008e6, the warning is emitted:
gcc/testsuite/gcc.dg/uninit-17.c: In function 'foo':
gcc/testsuite/gcc.dg/uninit-17.c:14:10: warning: '__real__ f' may be used
uninitialized [-Wmaybe-uninitialized]
14 | return f; /* { dg-warning "may be used" "unconditional" } */
| ^
gcc/testsuite/gcc.dg/uninit-17.c:7:5: note: '__real__ f' was declared here
7 | C f;
| ^
With basepoints/gcc-13-1762-gf9d4c3b45c5, it's silent.
Running the testcase on godbolt shows that the warning is available on builds
for x86-64 but not on builds for arm-none-eabi (GCC13 and above).
