From: Andrew Pinski <pinskia@physics.uc.edu>
To: Richard Henderson <rth@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR middle-end/17967, remove_useless_stmts is slow
Date: Fri, 15 Oct 2004 04:19:00 -0000 [thread overview]
Message-ID: <DE83364A-1E60-11D9-9E71-000A95D692F4@physics.uc.edu> (raw)
In-Reply-To: <20041014205231.GA25402@redhat.com>
On Oct 14, 2004, at 4:52 PM, Richard Henderson wrote:
> On Thu, Oct 14, 2004 at 02:36:41PM -0400, Andrew Pinski wrote:
>> * tree-cfg.c (remove_usless_stmts_cond): Fold statement.
>> (remove_useless_stmts_1): Fold trees we know how to fold.
>
> Ok.
I reverted it because I did not test fully and found that it
causes some regressions. Most of them are caused by fold (and
the C front-end which has other issues than talked about here)
not being able to fold &a[0]+1 into &a[1] unlike what fold_stmt
can do.
Why did someone put this part of the foldder into the fold_stmt
instead of fold I don't know (Diego was it you?).
Thanks,
Andrew Pinski
prev parent reply other threads:[~2004-10-15 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 18:37 Andrew Pinski
2004-10-14 21:01 ` Richard Henderson
2004-10-15 4:19 ` Andrew Pinski [this message]
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=DE83364A-1E60-11D9-9E71-000A95D692F4@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=rth@redhat.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).