public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/34949] Dead code in empty destructors.
Date: Wed, 03 Apr 2013 13:37:00 -0000	[thread overview]
Message-ID: <bug-34949-4-JHVf8YHIc1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-34949-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34949

--- Comment #26 from Jason Merrill <jason at gcc dot gnu.org> 2013-04-03 13:37:51 UTC ---
(In reply to comment #25)
> Looking at it more, if the change to emit *this ={v} {CLOBBER}; in cleanups
> rather than just at the end of function was desirable, then IMHO we just want
> to adjust the ehcleanup1.C testcase (from 4 to 6), those 2 removed regions are
> in a::~a where previously nothing has been cleaned up.

The change was desirable so that we can do DSE on the EH path as well as normal
control flow, as needed for 50243.  I've adjusted the testcase.


  parent reply	other threads:[~2013-04-03 13:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-34949-4@http.gcc.gnu.org/bugzilla/>
2011-02-09 22:44 ` pinskia at gcc dot gnu.org
2011-09-01  8:13 ` congruwer at yahoo dot co.uk
2011-09-01  9:10 ` rguenth at gcc dot gnu.org
2011-09-01  9:33 ` jakub at gcc dot gnu.org
2013-03-26 15:14 ` jason at gcc dot gnu.org
2013-03-26 15:20 ` jason at gcc dot gnu.org
2013-03-28 14:07 ` jakub at gcc dot gnu.org
2013-03-28 14:09 ` jakub at gcc dot gnu.org
2013-03-28 16:11 ` paolo.carlini at oracle dot com
2013-03-28 23:58 ` paolo.carlini at oracle dot com
2013-04-02 21:11 ` jason at gcc dot gnu.org
2013-04-03  6:31 ` jakub at gcc dot gnu.org
2013-04-03  6:31 ` jakub at gcc dot gnu.org
2013-04-03  6:31 ` jakub at gcc dot gnu.org
2013-04-03  9:27 ` schwab@linux-m68k.org
2013-04-03  9:39 ` jakub at gcc dot gnu.org
2013-04-03 12:28 ` jakub at gcc dot gnu.org
2013-04-03 13:37 ` jason at gcc dot gnu.org [this message]
2013-04-04  7:18 ` izamyatin at gmail dot com
2013-04-04  7:32 ` jakub at gcc dot gnu.org
2013-04-04  8:25 ` jakub at gcc dot gnu.org
2013-04-04  9:20 ` jakub at gcc dot gnu.org
2013-04-04 12:52 ` jakub at gcc dot gnu.org
2013-04-08 13:50 ` jakub at gcc dot gnu.org
2013-04-09 10:07 ` dimhen at gmail dot com
2008-01-23 23:23 [Bug middle-end/34949] New: Dead code in trivial destructors spark at gcc dot gnu dot org
2008-01-23 23:24 ` [Bug c++/34949] Dead code in empty destructors pinskia at gcc dot gnu dot org
2008-01-24  0:13 ` spark at gcc dot gnu dot org
2008-01-24 11:03 ` rguenth at gcc dot gnu dot org
2008-01-24 18:57 ` spark at gcc dot gnu dot org
2008-01-24 18:58 ` pinskia at gcc dot gnu dot org
2009-06-09 10:18 ` pinskia at gcc dot gnu dot 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-34949-4-JHVf8YHIc1@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).