This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/68164] Destructor side effect unexpectedly elided
- From: "webrown.cpp at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 02 Nov 2015 22:22:16 +0000
- Subject: [Bug c++/68164] Destructor side effect unexpectedly elided
- Auto-submitted: auto-generated
- References: <bug-68164-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68164
W E Brown <webrown.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from W E Brown <webrown.cpp at gmail dot com> ---
(In reply to Casey Carter from comment #3)
...
> The access to bp[i].data in the for loop inside the catch clause is the
> access to which I was referring.
...
Sorry, that hadn't been clear to me from the original response; I'd thought it
was discussing use of the this pointer.
I'm told that the original test program was earlier today adapted to avoid the
reported behavior. I haven't yet tried the revised version, but am closing
this report.