https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53917
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
CC| |msebor at gcc dot gnu.org
Status|NEW |RESOLVED
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
The underlying problem with the test case in comment #1 is the same as the one
discussed in bug 40635 comment #13. With the patch there applied, GCC issues a
note after the warning that points to the uninitialized variable:
pr53917-c1.c: In function ‘fn4’:
pr53917-c1.c:38:8: warning: ‘valid’ may be used uninitialized
[-Wmaybe-uninitialized]
38 | if (fn3 (&p_t1_rw_fsm_data.tag_mem_config))
| ^
pr53917-c1.c:25:9: note: ‘valid’ was declared here
25 | int valid;
| ^~~~~
There may be more that can be done to improve the context of the warning to
make it clearer but we can track those improvements separately.
*** This bug has been marked as a duplicate of bug 40635 ***
