https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43167
--- Comment #19 from Manuel López-Ibáñez <lopezibanez at gmail dot com> --- I think the solution is to have more locations. If the diagnostic code knew where the user value came from then it will know to not suppress the diagnostic. I wonder what happens if you used something that actually has a location, like an expression, for the first test case using emplace(). On Fri, 22 Mar 2019, 15:33 redi at gcc dot gnu.org, < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43167 > > --- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> --- > From Matthias Kretz on IRC: > > GCC needs to make a difference between warnings that apply when reading the > system headers and warnings that only manifest on a template instantiation > or > constprop > > -- > You are receiving this mail because: > You are on the CC list for the bug.
