[Bug libstdc++/50871] [C++0x] G++ fails to reject explicitly-defaulted function definition with different exception spec in system headers

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50871

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2014-04-04
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This bug hides the fact that we've apparently always been missing exception
specs on the operator== and operator!= for std::allocator.

Clang noticed this:

/home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/20_util/headers/memory/synopsis.cc:27:8:
error: exception specification in declaration does not match previous
declaration
/home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/20_util/headers/memory/synopsis.cc:29:8:
error: exception specification in declaration does not match previous
declaration
2 errors generated.

I'll look into using -pedantic when building the library and maybe for some of
the testsuite.