public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44883] Combine separate shift and add instructions into a single one
Date: Thu, 08 Jul 2010 23:22:00 -0000 [thread overview]
Message-ID: <20100708232219.30285.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44883-17659@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pinskia at gcc dot gnu dot org 2010-07-08 23:22 -------
>So in function fwprop_addr before deciding propagate an expression should we
also check if it is the only use of the corresponding def?
It does somewhat. Though address cost might be lower for r2+r3 than just r8.
Please make sure that fwprop_addr has the correct address cost.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|rtl-optimization |target
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44883
next prev parent reply other threads:[~2010-07-08 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 23:18 [Bug rtl-optimization/44883] New: " carrot at google dot com
2010-07-08 23:22 ` pinskia at gcc dot gnu dot org [this message]
2010-07-09 0:04 ` [Bug target/44883] " carrot at google dot com
2010-07-09 0:06 ` pinskia at gcc dot gnu dot org
2010-07-09 22:11 ` carrot at google dot com
[not found] <bug-44883-4@http.gcc.gnu.org/bugzilla/>
2021-09-26 22:43 ` pinskia 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=20100708232219.30285.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).