From: "Naveen Sharma, Noida" <naveens@noida.hcltech.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, Michael Matz <matz@suse.de>
Subject: Re: Dead-code elimination can't remove string copy insns?
Date: Wed, 14 May 2003 11:34:00 -0000 [thread overview]
Message-ID: <E04CF3F88ACBD5119EFE00508BBB212109461B5E@exch-01.noida.hcltech.com> (raw)
> >> but the alias information should be sufficient to see that
> the memory region being written into is on the stack, and unused past
> this insn, hence the store is dead and can be deleted.
>
> > It should, but we don't do that currently.
>
> Do you have a sense for how hard this would be to implement? Is it
> something that's done on tree-ssa, so there's no point adding it in
> mainline? Will Naveen's stack-slot allocator help?
The stack pseudos rely on the flow infrastructure.
At the moment, the dead stores to the stack should be removed
in the tail blocks (but not for BLKmode mems).
But it should be simple to teach flow analysis to handle this
case with stack pseudos.
Best Regards,
Naveen Sharma.
next reply other threads:[~2003-05-14 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 11:34 Naveen Sharma, Noida [this message]
-- strict thread matches above, loose matches on Subject: below --
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 22:14 ` Richard Henderson
2003-05-14 9:25 ` Michael Matz
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=E04CF3F88ACBD5119EFE00508BBB212109461B5E@exch-01.noida.hcltech.com \
--to=naveens@noida.hcltech.com \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
--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).