From: Jakub Jelinek <jakub@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>, gcc-patches@gcc.gnu.org
Subject: Re: fix left-over debug insns in DCE
Date: Mon, 06 Jun 2011 06:05:00 -0000 [thread overview]
Message-ID: <20110606060439.GO17079@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <or7h8zed8y.fsf@livre.localdomain>
On Mon, Jun 06, 2011 at 02:32:29AM -0300, Alexandre Oliva wrote:
> Those that remove sets whose DESTs may still be receved by debug insns
> ought to adjust debug insns, yeah. I think (hope) we have them all
> covered. Do you know of any we missed?
delete_trivially_dead_insns is already covered, fast DCE is what I've
encountered to be missing in the past (see PR48886), but I guess your
patch covers both fast DCE and ud DCE.
Jakub
next prev parent reply other threads:[~2011-06-06 6:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 12:15 Alexandre Oliva
2011-06-02 15:26 ` Eric Botcazou
2011-06-03 1:16 ` Alexandre Oliva
2011-06-03 11:06 ` Eric Botcazou
2011-06-06 5:38 ` Alexandre Oliva
2011-06-06 6:05 ` Jakub Jelinek [this message]
2011-06-06 8:00 ` Eric Botcazou
2011-06-06 10:07 ` Alexandre Oliva
2011-06-06 13:28 ` Alexandre Oliva
2011-06-07 12:25 ` [PATCH] Fix ICE in reset_unmarked_insns_debug_uses (PR middle-end/49308) Jakub Jelinek
2011-06-09 8:04 ` Jakub Jelinek
2012-04-09 6:14 ` fix left-over debug insns in DCE Alexandre Oliva
2012-04-09 13:42 ` Eric Botcazou
2012-04-13 15:59 ` Alexandre Oliva
2012-04-13 16:45 ` Paolo Bonzini
2012-05-03 18:27 ` [PR52983] eliminate autoinc from debug_insn locs (was: Re: fix left-over debug insns in DCE) Alexandre Oliva
2012-05-03 22:40 ` [PR52983] eliminate autoinc from debug_insn locs Alexandre Oliva
2012-06-13 8:01 ` Alexandre Oliva
2012-07-02 12:29 ` Alexandre Oliva
2012-05-03 22:46 ` [PR52983, PR48866] " Alexandre Oliva
2012-06-13 8:56 ` Alexandre Oliva
2012-06-13 9:15 ` Jakub Jelinek
2011-06-06 7:11 ` fix left-over debug insns in DCE Alexandre Oliva
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=20110606060439.GO17079@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=aoliva@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@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).