public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hstong at ca dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53868] New: Temporary for indirect binding is not destroyed when destructor from initializer temp throws Date: Fri, 06 Jul 2012 03:21:00 -0000 [thread overview] Message-ID: <bug-53868-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53868 Bug #: 53868 Summary: Temporary for indirect binding is not destroyed when destructor from initializer temp throws Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: hstong@ca.ibm.com Host: powerpc64-unknown-linux-gnu Target: powerpc64-unknown-linux-gnu The temporary created for indirect binding should be completely constructed (and from the output _it is_) before the destructors for temporaries in the initializer are called. In the following case, the destructor for a temporary in the initializer throws an int. During stack unwinding, it seems the temporary bound to the reference is missed. ### Self-contained source:> cat tempbindIndirect_inittempDtorThrows.cpp extern "C" int printf(const char *, ...); extern "C" void abort(); struct SubobjectInA { SubobjectInA(); ~SubobjectInA(); }; struct A : SubobjectInA { A() = delete; A(const A &) = delete; A(A &&) { } A(int); ~A(); }; #define TRACE_FUNC( ... ) \ { printf("%s\n", __PRETTY_FUNCTION__); __VA_ARGS__ } struct Q { Q() : q(0) TRACE_FUNC() ~Q(); int q; }; int main() { try { const A &a = Q().q; } catch (...) { return 0; } abort(); } SubobjectInA::SubobjectInA() TRACE_FUNC() SubobjectInA::~SubobjectInA() TRACE_FUNC() A::A(int) TRACE_FUNC() A::~A() TRACE_FUNC() Q::~Q() TRACE_FUNC( throw 0; ) ### Compiler invocation: g++-4.7.0 -std='c++11' tempbindIndirect_inittempDtorThrows.cpp -o test ### Compiler output: (return code 0) ### Output from resulting executable:> ./test ; echo rc=$? Q::Q() SubobjectInA::SubobjectInA() A::A(int) Q::~Q() rc=0 ### Expected output: Q::Q() SubobjectInA::SubobjectInA() A::A(int) Q::~Q() A::~A() SubobjectInA::~SubobjectInA() rc=0 ### gcc -v output:> g++-4.7.0 -v Using built-in specs. COLLECT_GCC=g++-4.7.0 COLLECT_LTO_WRAPPER=/data/gcc/libexec/gcc/powerpc64-unknown-linux-gnu/4.7.0/lto-wrapper Target: powerpc64-unknown-linux-gnu Configured with: ../gcc-4.7.0/configure --prefix=/data/gcc --program-suffix=-4.7.0 --disable-libssp --disable-libgcj --enable-version-specific-runtime-libs --with-cpu=default32 --enable-secureplt --with-long-double-128 --enable-shared --enable-__cxa_atexit --enable-threads=posix --enable-languages=c,c++,fortran --with-mpfr=/usr/local/ --with-mpc=/usr/local/ --with-gmp=/usr/local/ Thread model: posix gcc version 4.7.0 (GCC)
next reply other threads:[~2012-07-06 3:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-06 3:21 hstong at ca dot ibm.com [this message] 2012-07-06 8:17 ` [Bug c++/53868] " redi at gcc dot gnu.org 2021-08-27 9:36 ` pinskia at gcc dot gnu.org 2022-01-06 21:47 ` jason at gcc dot gnu.org 2022-01-07 0:26 ` cvs-commit at gcc dot gnu.org 2022-01-28 4:34 ` jason at gcc dot gnu.org
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-53868-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: linkBe 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).