public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avi@cloudius-systems.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61982] Optimizer does not eliminate stores to destroyed objects Date: Fri, 01 Aug 2014 16:32:00 -0000 [thread overview] Message-ID: <bug-61982-4-9iFdQ9P6In@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61982-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61982 --- Comment #3 from Avi Kivity <avi@cloudius-systems.com> --- I observed this with non-trivial destructors as well. In fact, something like: X::~X() { i = 3; } also emits a store.
next prev parent reply other threads:[~2014-08-01 16:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-31 18:54 [Bug c++/61982] New: " avi@cloudius-systems.com 2014-08-01 8:24 ` [Bug c++/61982] " rguenth at gcc dot gnu.org 2014-08-01 15:12 ` jakub at gcc dot gnu.org 2014-08-01 16:32 ` avi@cloudius-systems.com [this message] 2014-08-01 16:52 ` glisse at gcc dot gnu.org 2014-08-01 17:10 ` avi@cloudius-systems.com 2014-08-01 18:10 ` daniel.kruegler at googlemail dot com
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-61982-4-9iFdQ9P6In@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).