From: Dale Johannesen <dalej@apple.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Dale Johannesen <dalej@apple.com>, gcc@gcc.gnu.org
Subject: Re: Dead-code elimination can't remove string copy insns?
Date: Tue, 13 May 2003 00:48:00 -0000 [thread overview]
Message-ID: <731C93BE-84DC-11D7-BAEF-000393D76DAA@apple.com> (raw)
In-Reply-To: <87addrpu7r.fsf@egil.codesourcery.com>
On Monday, May 12, 2003, at 05:26 PM, Zack Weinberg wrote:
> Why can't anything delete these insns? I'm guessing it has something
> to do with the BLKmode memory access, 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.
Can it tell the region's address hasn't been taken and stored somewhere?
> Full dumps on request. The above snippets are from the .life dump.
> The input file is gcc.dg/const-elim-1.c.
next prev parent reply other threads:[~2003-05-13 0:48 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 [this message]
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
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=731C93BE-84DC-11D7-BAEF-000393D76DAA@apple.com \
--to=dalej@apple.com \
--cc=gcc@gcc.gnu.org \
--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).