linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: gcc-help@gcc.gnu.org, kernel mailz <kernelmailz@googlemail.com>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Inline assembly queries [2]
Date: Tue, 07 Jul 2009 14:40:02 +0200	[thread overview]
Message-ID: <m37hykis4d.fsf@hase.home> (raw)
In-Reply-To: <20090706065627.GA12499@iram.es> (Gabriel Paubert's message of "Mon, 6 Jul 2009 08:56:27 +0200")

Gabriel Paubert <paubert@iram.es> writes:

> On Fri, Jul 03, 2009 at 10:57:12PM +0200, Andreas Schwab wrote:
>> The 'Z' constraint is required for a memory operand for insns that don't
>> have an update form (which would be selected by the %U modifier).  
>
> Hmmm, I believed that it was for instructions that only have an indexed
> form (all Altivec, byte reverse, and l?arx/st?cx for atomic operations).
>
> Of course none of these instructions have an update form, but they don't
> have an offset encoded in the instruction either.

Yes, you are right.  IIRC there are either all u/x/ux forms or only the
x form.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2009-07-07 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  6:44 Inline assembly queries [2] kernel mailz
2009-07-03 17:40 ` Brad Boyer
2009-07-03 20:05   ` kernel mailz
2009-07-03 21:19     ` Andreas Schwab
2009-07-03 20:57   ` Andreas Schwab
2009-07-06  6:56     ` Gabriel Paubert
2009-07-07 12:40       ` Andreas Schwab [this message]
2009-07-07 13:46         ` Gabriel Paubert

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=m37hykis4d.fsf@hase.home \
    --to=schwab@linux-m68k.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kernelmailz@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paubert@iram.es \
    /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 NNTP newsgroup(s).