[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

--- Comment #3 from jason dot orendorff at gmail dot com 2009-05-20 14:33 --- I should clarify that in the real-world case, the apparently relevant declaration doesn't use ... at all, hence the tentative diagnosis of "something weird". -- http://gcc.gnu.org/bugzil

[Bug c++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called

--- Comment #2 from jason dot orendorff at gmail dot com 2009-05-20 14:28 --- No, I'm asking for the extra line: nonpod.cpp:1: calling `void f(...)' declared here -- jason dot orendorff at gmail dot com changed: What|Removed

[Bug c++/40202] New: warning about passing non-POD objects through �...� should include name and location of declaration being called

dot gnu dot org ReportedBy: jason dot orendorff at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202

[Bug c/26542] bogus diagnostic with -pedantic?: format '%p'; expects type 'void*', but argument 2 has type 'A*'

--- Comment #9 from jason dot orendorff at gmail dot com 2009-02-10 22:22 --- Please consider reopening this bug. I appreciate that the relevant standards don't guarantee this idiom will always work. On the other hand, this warning is in practice only a nuisance. Balance the