https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118216
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The obvious workaround is just initialize symval to 0. Basically the missed optimization is causing the uninitialized variable warning to become confused when it comes dealing with sym_sec and not seeing the use of symval cannot happen if sym_sec is known to be null.