[Bug c++/86562] Missing warning (error in C++11) for passing nontrivial object to varargs function via function pointer

2018-07-18 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86562

Jonathan Wakely  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |INVALID

--- Comment #3 from Jonathan Wakely  ---
I disagree. This report states "g++ accepts it, but clang++ rejects it" and
that is not a bug, it's a feature. If a diagnostic is desired it can be
requested with -Wconditionally-supported or -Werror-conditionally-supported

64867 says "It would be nice to have a distinct warning flag for this feature"
which is different.

This bug is invalid.

[Bug c++/86562] Missing warning (error in C++11) for passing nontrivial object to varargs function via function pointer

2018-07-18 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86562

Eric Gallager  changed:

   What|Removed |Added

   Keywords||diagnostic
 CC||egallager at gcc dot gnu.org
 Resolution|INVALID |DUPLICATE

--- Comment #2 from Eric Gallager  ---
I think this is actually a dup of bug 64867

*** This bug has been marked as a duplicate of bug 64867 ***

[Bug c++/86562] Missing warning (error in C++11) for passing nontrivial object to varargs function via function pointer

2018-07-18 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86562

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Jonathan Wakely  ---
Not a bug. The standard says passing non-trivial types through varargs is
"conditionally-supported" so an implementation can either support it, or reject
it with a diagnostic.

GCC supports it, Clang doesn't.