Hi On Mon, Sep 30, 2024 at 12:15 PM <marcandre.lur...@redhat.com> wrote: > > From: Marc-André Lureau <marcandre.lur...@redhat.com> > > Hi, > > Depending on -Doptimization=<value>, GCC (14.2.1 here) produces different > maybe-uninitialized warnings: > - g: produces -Werror=maybe-uninitialized errors > - 0: clean build > - 1: produces -Werror=maybe-uninitialized errors > - 2: clean build > - 3: produces few -Werror=maybe-uninitialized errors > - s: produces -Werror=maybe-uninitialized errors > > Most are false-positive, because prior LOCK_GUARD should guarantee an > initialization path. Few of them are a bit trickier. Finally, I found > a potential related memory leak. > > Patches missing r-b: 6, 10-11, 15-21
Patches missing review: 16, 20, 21. "target/loongarch: fix -Werror=maybe-uninitialized false-positive" "block: fix -Werror=maybe-uninitialized false-positive" "qom/object: fix -Werror=maybe-uninitialized" thanks!
