From: "Michael S. Zick" <mszick@goquest.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Should I read SHR[DW] as SHRP[DW] in parisc2.pdf?
Date: Thu, 12 Aug 2004 14:33:15 -0500 [thread overview]
Message-ID: <200408121433.15444.mszick@goquest.com> (raw)
In-Reply-To: <200408121741.KAA29481@lucy.cup.hp.com>
On Thu August 12 2004 12:41, Jim Hull wrote:
> Joel:
>
- - - - -
>
> Does the PA2.0 gnu assembler not recognize these (and other) pseudo-ops?
Perhaps too well.
If I recall properly, the same table & code is used for both the assembler and
the 'disassemble' (-d) option of objdump.
'objdump -d' tries to be explicit in showing the space register assumed...
but it also displays the pseudo operations rather than the actual operation.
(Grumble, Grumble)
I think that Joel's question comes from (his and my) wondering if we need to
make 'machine independent' defines of some of these instructions.
According to Appendix J - we don't - the PA1.1 codes will assemble for
PA2.0 (with HP's assembler).
Time will show if gcc-inline assembly is that nice to we programmers.
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-08-12 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 17:35 [parisc-linux] Should I read SHR[DW] as SHRP[DW] in parisc2.pdf? Joel Soete
2004-08-12 17:41 ` Jim Hull
2004-08-12 19:33 ` Michael S. Zick [this message]
2004-08-13 15:20 ` [parisc-linux] Should I read SHR[DW] as SHRP[DW] in parisc2.p John David Anglin
2004-08-13 17:50 ` Michael S. Zick
2004-08-13 22:54 ` [parisc-linux] Should I read SHR[DW] as SHRP[DW] in parisc2.pdf? Michael S. Zick
2004-08-14 0:27 ` [parisc-linux] Should I read SHR[DW] as SHRP[DW] in parisc2.p John David Anglin
2004-08-14 0:53 ` Michael S. Zick
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=200408121433.15444.mszick@goquest.com \
--to=mszick@goquest.com \
--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