From: Julian Brown <julian@codesourcery.com>
To: Michael Hope <michaelh@juju.net.nz>
Cc: gcc@gcc.gnu.org
Subject: Re: Using a umulhisi3
Date: Wed, 03 Jun 2009 09:55:00 -0000 [thread overview]
Message-ID: <20090603105538.3d340a7c@rex.config> (raw)
In-Reply-To: <31d002d40906030239m3e6708b1xd89105c19105c1ab@mail.gmail.com>
On Wed, 3 Jun 2009 21:39:34 +1200
Michael Hope <michaelh@juju.net.nz> wrote:
> How does the combine stage work? It looks like it could get multiple
> potential matches for a set of RTLs. Does it use some type of costing
> function to pick between them? Can I tell combine that a umulhisi3 is
> cheaper than a mulsi3?
You could try defining TARGET_RTX_COSTS, if you haven't already.
Julian
prev parent reply other threads:[~2009-06-03 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 9:39 Michael Hope
2009-06-03 9:55 ` Julian Brown [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=20090603105538.3d340a7c@rex.config \
--to=julian@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=michaelh@juju.net.nz \
/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).