public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Pseudo-ops: IAS versus ia64-hp-linux-as
Date: Wed, 30 Jan 2002 22:20:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805967@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805959@msgid-missing>

>  Does the ia64-hp-linux-as assembler which comes with the
> Ski/NUE support all pseudo-ops as done by the 
> Intel Assembler IAS , [ as given in the Assembler Users Guide]
> ?

GNU as follows the assembler and architecture documentation.  There are
some differences in syntax from IAS because IAS doesn't always follow the
documentation.  No one has really tried to figure out whether IAS or the
docs are wrong, we just follow the docs.  There are only a couple of
minor differences though which are easy to work around.

GNU as supports all of the pseudo-ops, and most of the directives.  I don't
know of anyone who has tried to verify this, so there could be some obscure
ones missing.  Some of the optional directives are deliberately not
immplemented.  These are mostly the directives for performing register
allocation in the assembler.  GNU as doesn't do register allocation, nor
do we think it should.  Also, .org is not implemented since GNU ld can't
support it.

> The Guide is unclear about what the ld8.mov instruction
> does. Can somebody explain this to me ?

There is ld8.mov instruction.  Perhaps you mean ld8.fill?  See the Software
Developers Manual, which explains what every instruction does.  See also
the explanation of the register stack engine and NaT bits, which us what
ld8.fill is used for.

Jim



  reply	other threads:[~2002-01-30 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 16:34 [Linux-ia64] Pseudo-ops: IAS versus ia64-hp-linux-as HARISH J PRABHU
2002-01-30 22:20 ` Jim Wilson [this message]
2002-01-31  6:12 ` Christian Hildner
2002-01-31 17:14 ` Refah, Azita
2002-02-05 21:13 ` Jim Wilson

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=marc-linux-ia64-105590698805967@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@vger.kernel.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