Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: dave@hiauly1.hia.nrc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Gcc bug or I missunderstand? [ftsd %fr22, 56(%sr0, %r20) failed to build?]
Date: Wed, 15 Dec 2004 11:04:36 -0700	[thread overview]
Message-ID: <20041215180436.GD27818@colo.lackof.org> (raw)
In-Reply-To: <20041215171813.GA28058@parcelfarce.linux.theplanet.co.uk>

On Wed, Dec 15, 2004 at 05:18:13PM +0000, Matthew Wilcox wrote:
> Quick look at page 9-24 of the Kane book indicates that for d between +15
> and -16 we use format 42 and for d outside that range, we use format 3.
> Looks like nobody bothered to teach binutils about this longer form yet.
> Is it possible it's only available for PA2.0 processors?

Yes - that seems to be the case.
FSTD is PA2.0 Mnemonic. Page J-4 of the same book.

The two corresponding PA 1.1 ops are FSTDS and FSTDX.
FSTDS is the short form (5 bits immediate).
We could use FSTDX but it will require another register in the asm.

grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-12-15 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 16:27 [parisc-linux] Gcc bug or I missunderstand? [ftsd %fr22, 56(%sr0, %r20) failed to build?] Joel Soete
2004-12-15 16:39 ` [parisc-linux] " Randolph Chung
2004-12-15 17:18   ` Matthew Wilcox
2004-12-15 18:04     ` Grant Grundler [this message]
2004-12-15 18:25       ` Joel Soete
2004-12-15 19:12         ` [parisc-linux] Re: Gcc bug or I missunderstand? [ftsd %fr22, John David Anglin
2004-12-15 19:01     ` John David Anglin

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=20041215180436.GD27818@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@lists.parisc-linux.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