public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34503] Issues with constant/copy propagation implementation in gcse.c
Date: Mon, 17 Dec 2007 08:20:00 -0000 [thread overview]
Message-ID: <20071217082021.21265.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34503-280@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from steven at gcc dot gnu dot org 2007-12-17 08:20 -------
Local const/copy propagation uses cselib, which is too heavy-weight for
something this simple. The reason for using cselib is that, at the time, we
also tried to do local CSE with cselib. But this never worked and we ended up
with cselib for just recording constants and copies. This could be done much
more efficiently with a simple mapping of registers to constants and copies.
--
steven at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-12-17 08:20:21
date| |
Summary|Issues with constant/copy |Issues with constant/copy
|propagation implementation |propagation implementation
|in gcse.c |in gcse.c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34503
next prev parent reply other threads:[~2007-12-17 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 8:17 [Bug rtl-optimization/34503] New: " steven at gcc dot gnu dot org
2007-12-17 8:20 ` steven at gcc dot gnu dot org [this message]
2007-12-17 8:22 ` [Bug rtl-optimization/34503] " steven at gcc dot gnu dot org
2007-12-17 8:31 ` steven at gcc dot gnu dot org
2007-12-17 8:38 ` steven at gcc dot gnu dot org
2007-12-17 8:41 ` steven at gcc dot gnu dot org
2007-12-17 8:42 ` steven at gcc dot gnu dot org
2008-05-24 14:32 ` steven at gcc dot gnu dot org
2010-02-12 22:00 ` steven at gcc dot gnu dot org
[not found] <bug-34503-4@http.gcc.gnu.org/bugzilla/>
2015-03-24 10:29 ` steven at gcc dot gnu.org
2015-04-24 4:50 ` thopre01 at gcc dot gnu.org
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=20071217082021.21265.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).