https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102196
Bug ID: 102196
Summary: -Wmaybe-uninitialized: Maybe generate helpful hints?
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jbg...@lug-owl.de
Target Milestone: ---
Hi!
I don't know the code behind -Wmaybe-uninitialized, but maybe it's possible to
show the path GCC considered when emitting this message?
Right now, with Debian's "gcc-snapshot" compiler, I cannot successfully "make
all-gas" for the microblaze-elf and mcore-elf targets (with current binutils at
0b99a66053fa1e93a984f75a7a3d5343c74882fb) due to a maybe-uninitialized warning
in md_assemble() which is kind of unpleasant to find the possible way through
the assignment maze...
My personal impression is that usually, the maybe-uninitialized warnings are
quite helpful, but it's somewhat tedious to track them down. As I'm revamping
my toolchain testing efforts, these show up every now and then.
Thanks,
Jan-Benedict
