From: Zack Weinberg <zack@codesourcery.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Michael Matz <matz@suse.de>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Dead-code elimination can't remove string copy insns?
Date: Tue, 13 May 2003 17:36:00 -0000 [thread overview]
Message-ID: <87k7cun3z5.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20030513170722.GA7112@tornado.toronto.redhat.com> (Diego Novillo's message of "Tue, 13 May 2003 13:07:22 -0400")
Diego Novillo <dnovillo@redhat.com> writes:
> On Tue, May 13, 2003 at 09:40:33AM -0700, Zack Weinberg wrote:
>
>> gcc.dg/const-elim-1.c. On an x86, compile it with -march=i386 -O2;
>> rs6000-ibm-aix5 and arm-elf also show the problem.
>>
> Yup, tree-ssa handles it. The original program in GIMPLE form is
> on the left. The optimized version is on the right (we still
> don't linearize GOTO_EXPRs).
Excellent. In that case I will not worry about getting const-elim-1.c
to work for all targets on the mainline. The present situation is not
a regression -- we just weren't testing for dead-constant removal
before.
Could those port maintainers seeing failures for const-elim-1.c please
apply patches to mark it XFAIL for their target?
zw
next prev parent reply other threads:[~2003-05-13 17:36 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 [this message]
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=87k7cun3z5.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
/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).