On Thu, Aug 17, 2023 at 9:00 PM Michael D Kinney <michael.d.kin...@intel.com> wrote: > > I am surprised this same GCC error is not being seen for other CPU archs. > > > > The simple fix is to this specific issue is to initialize CommandLine to NULL > at the beginning of the function.
The correct fix here is to -Wno-error=maybe-uninitialized. This warning is error prone and IIRC already disabled in the Linux kernel. Heck, Wno-error=uninitialized wouldn't be a bad idea either, we recently uncovered a GCC bug on it (https://lore.kernel.org/all/20230719190045.4007391-1-a...@kernel.org/). > > We have observed that compilers continue to add more and more static analysis > like features over time. Code that compiled without warnings/errors with an > earlier compiler may generate warnings/errors on a newer compiler. This > looks like an example of this case. Well, in this case the static analysis is wrong :) -- Pedro -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#107839): https://edk2.groups.io/g/devel/message/107839 Mute This Topic: https://groups.io/mt/100663199/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
