https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119251
--- Comment #5 from uecker at gcc dot gnu.org ---
Maybe a more targeted warning would make sense, e.g. taking the address of a
compound literal inside ({ }). Maybe even checking whether it escapes? And/or
only inside macros?
