[Bug libstdc++/68139] rethrow_if_nested should tolerate overloaded unary operator

[ville at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68139

--- Comment #3 from ville at gcc dot gnu.org ---
Author: ville
Date: Fri Dec 11 12:04:23 2015
New Revision: 231562

URL: https://gcc.gnu.org/viewcvs?rev=231562=gcc=rev
Log:
PR libstdc++/68139

Added:
trunk/libstdc++-v3/testsuite/18_support/nested_exception/68139.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/libsupc++/nested_exception.h

[Bug libstdc++/68139] rethrow_if_nested should tolerate overloaded unary operator

[ville.voutilainen at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68139

Ville Voutilainen  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Ville Voutilainen  ---
Done.

[Bug libstdc++/68139] rethrow_if_nested should tolerate overloaded unary operator

[ville.voutilainen at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68139

Ville Voutilainen  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||ville.voutilainen at gmail dot 
com
   Assignee|unassigned at gcc dot gnu.org  |ville.voutilainen at 
gmail dot com

--- Comment #2 from Ville Voutilainen  ---
Mine.

[Bug libstdc++/68139] rethrow_if_nested should tolerate overloaded unary operator

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68139

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2015-10-31
 Ever confirmed|0   |1

[Bug libstdc++/68139] rethrow_if_nested should tolerate overloaded unary operator

[daniel.kruegler at googlemail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68139

Daniel Krügler  changed:

   What|Removed |Added

 CC||daniel.kruegler@googlemail.
   ||com

--- Comment #1 from Daniel Krügler  ---
Your argumentation is a bit flawed because the standard never guarantees that
address values within library code implicitly are required to use
std::addressof - the library specification needs to say that explicitly. But in
this case I agree that the library needs to handle that case. The reason for
this is, because the *specification* of rethrow_if_nested doesn't say anything
about the need to determine address values.