public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: "Mohamed Bamakhrama" <bamakhrama@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC Assembler Modifiers
Date: Thu, 14 Jun 2007 13:40:00 -0000	[thread overview]
Message-ID: <18033.17195.831402.821720@zebedee.pink> (raw)
In-Reply-To: <40378e40706140614q5cce06b6tbf21cea41d2e1e6a@mail.gmail.com>

Mohamed Bamakhrama writes:

 > I have two questions related to the modifiers that can be used with
 > operands in inline assembly.
 > 1) What does the 'z' mean when added to the operand modifier (e.g. %z0)?

From i386.md:

;; The special asm out single letter directives following a '%' are:
;; 'z' mov%z1 would be movl, movw, or movb depending on the mode of
;;     operands[1].
;; 'L' Print the opcode suffix for a 32-bit integer opcode.
;; 'W' Print the opcode suffix for a 16-bit integer opcode.
;; 'B' Print the opcode suffix for an 8-bit integer opcode.
;; 'Q' Print the opcode suffix for a 64-bit float opcode.
;; 'S' Print the opcode suffix for a 32-bit float opcode.
;; 'T' Print the opcode suffix for an 80-bit extended real XFmode float opcode.
;; 'J' Print the appropriate jump operand.
;;

 > 2) In the Input operands list, what is the meaning of 'J' (e.g. ... :
 > .... : "Jr" (0) )?

See 14.8, Register Classes, in the gcc internals manual.

The machine-dependent operand constraint letters (`I', `J', `K',
... `P') specify particular ranges of integer values.

Also, see constraints.md:

(define_constraint "J"
  "Integer constant in the range 0 ... 63, for 64-bit shifts."
  (and (match_code "const_int")
       (match_test "IN_RANGE (ival, 0, 63)")))

Andrew.

  reply	other threads:[~2007-06-14 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 13:39 Mohamed Bamakhrama
2007-06-14 13:40 ` Andrew Haley [this message]
2007-06-14 13:42   ` Mohamed Bamakhrama
2007-06-14 15:49     ` Andrew Haley
2007-06-14 14:41 ` Segher Boessenkool

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=18033.17195.831402.821720@zebedee.pink \
    --to=aph-gcc@littlepinkcloud.com \
    --cc=bamakhrama@gmail.com \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).