https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114285
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Given GCC considers memory to be initialized when you write to it and copying from A to B involves a write to B the uninit info would be lost if A is uninitialized. So IMO it's reasonable to diagnose a copy from uninitialized, at least unless you can fully analyze all possible uses of B (which, when B is memory is unlikely). Note that's not the analyzer-specific opinion but viewed from the -Wuninitialized implementation point of view.
