public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "webrown.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68164] New: Destructor side effect unexpectedly elided
Date: Fri, 30 Oct 2015 17:25:00 -0000 [thread overview]
Message-ID: <bug-68164-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68164
Bug ID: 68164
Summary: Destructor side effect unexpectedly elided
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: webrown.cpp at gmail dot com
Target Milestone: ---
Created attachment 36625
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36625&action=edit
Test program
Compiler version: g++-mp-6 (MacPorts gcc6 6-20151025_0) 6.0.0 20151025
(experimental).
Compiling via: g++-mp-6 -Og -std=c++1z
The enclosed test program improperly asserts because (it seems) that the
assignment in the body of B's destructor is elided.
The program does not assert, however, if I insert a debugging output statement
(marked #1) following the assignment.
Comment #1 out to see the unexpected failed assertion. Repositioning #1 to
precede the assignment also results in a failed assertion.
reply other threads:[~2015-10-30 17:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-68164-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).