From: Michael Matz <matz@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: Zack Weinberg <zack@codesourcery.com>, <gcc@gcc.gnu.org>
Subject: Re: Dead-code elimination can't remove string copy insns?
Date: Wed, 14 May 2003 09:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0305141118170.15564-100000@wotan.suse.de> (raw)
In-Reply-To: <20030513215528.GE8273@redhat.com>
Hi,
On Tue, 13 May 2003, Richard Henderson wrote:
> On Tue, May 13, 2003 at 11:30:12AM +0200, Michael Matz wrote:
> > Exactly. We don't track dead stores to memory.
>
> Well, we do, but it only works on tail blocks.
I know. But this uses the mem expressions to represent the stored-into
memory, and hence doesn't work on BLKmode mems. I guess one could special
case Zacks example by noting (for the tail blocks), that all stores to
stack mem are dead if there is _no_ read from stack afterwards. But this
special casing quickly becomes silly.
Ciao,
Michael.
next prev parent reply other threads:[~2003-05-14 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:26 Zack Weinberg
2003-05-13 0:48 ` Dale Johannesen
2003-05-13 1:30 ` Zack Weinberg
2003-05-13 9:30 ` Michael Matz
2003-05-13 16:17 ` Zack Weinberg
2003-05-13 16:30 ` Diego Novillo
2003-05-13 16:40 ` Zack Weinberg
2003-05-13 17:07 ` Diego Novillo
2003-05-13 17:16 ` law
2003-05-13 17:24 ` Diego Novillo
2003-05-13 17:36 ` Zack Weinberg
2003-05-13 17:38 ` law
2003-05-13 17:50 ` Diego Novillo
2003-05-13 18:02 ` law
2003-05-13 18:35 ` Joe Buck
2003-05-13 19:35 ` [tree-ssa] Improve eliminate_useless_stmts_and_vars [Was Re: Dead-code elimination can't remove string copy insns? ] law
2003-05-13 22:14 ` Dead-code elimination can't remove string copy insns? Richard Henderson
2003-05-14 9:25 ` Michael Matz [this message]
2003-05-14 11:34 Naveen Sharma, Noida
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=Pine.LNX.4.44.0305141118170.15564-100000@wotan.suse.de \
--to=matz@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=zack@codesourcery.com \
/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).