From: Steve Ellcey <sje@cup.hp.com>
To: joern.rennecke@superh.com
Cc: gcc@gcc.gnu.org
Subject: Re: IA64 floating point division question
Date: Wed, 01 Sep 2004 17:51:00 -0000 [thread overview]
Message-ID: <200409011751.KAA16738@hpsje.cup.hp.com> (raw)
In-Reply-To: <200409011209.i81C98n10992@chloe.uk.w2k.superh.com>
> > (set (scratch:BI)
> > (unspec:BI [
> > (reg:SF 349 [ a ])
> > (reg:SF 350 [ b ])
> > ] 14))
>
> 'scratch' will probably fail to match your operand predicate.
> match_scratch is no good if you want your pattern to be split before
> reload. Instead, you have to use match_operand, and make your expander
> allocate a pseudo register and stick it into the scratch operand.
Ah, that's the piece of the puzzle I was missing.
Thank you,
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2004-09-01 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 23:20 Steve Ellcey
2004-08-31 23:58 ` Zack Weinberg
2004-09-01 12:25 ` Joern Rennecke
2004-09-01 12:28 ` Joern Rennecke
2004-09-01 17:51 ` Steve Ellcey [this message]
[not found] <200408312358.QAA26610@hpsje.cup.hp.com>
2004-09-01 0:10 ` Zack Weinberg
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=200409011751.KAA16738@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@superh.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).