File this first with gdb as it is gdb's sources which are have the warning in it, if they say the warning is bogus, file a real bug report with the preprocessed source.

 (In reply to comment #1)
> File this first with gdb as it is gdb's sources which are have the warning in
> it, if they say the warning is bogus, file a real bug report with the
> preprocessed source.
 
When you look at the code, the warning is obviously spurious.
But we know that uninitialized warnings cannot be made reliable, so it is
unclear if you can call it bogus.
With the bootstrap building gdb with -Wuninitailized -Werror, we are basically asking for trouble.
AFAIK we have not documented any conding standards that tell how to write
code that can be compiled successfully with these options, so it seems disingenious to put the blame on the code in gdb.