From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: James Hogan <james.hogan@imgtec.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Fix write_gc0_* macros when writing zero
Date: Fri, 20 May 2016 15:13:11 +0200 [thread overview]
Message-ID: <20160520131310.GA13016@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1605200920370.6794@tp.orcam.me.uk>
On Fri, May 20, 2016 at 09:31:15AM +0100, Maciej W. Rozycki wrote:
> On Fri, 20 May 2016, James Hogan wrote:
>
> > > NB `z' here is an "operand code" in GCC-speak. There's a list of the
> > > MIPS-specific ones in gcc/config/mips/mips.c above `mips_print_operand'.
> > > There are a few generic operand codes as well, most notably `a' to print
> > > an address, matching the `p' constraint. I think it would be good to have
> > > this all documented in the GCC manual sometime.
> >
> > Thanks Maciej! To be honest I pretty much guessed at what they were
> > called. Good to see 'z' does do what I thought. I couldn't find any
> > documentation online for the MIPS specific operand codes, so having them
> > documented with GCC would be an excellent idea!
>
> Yeah, this stuff is a bit obscure (the other one being %-sequences for
> the specs) and I always find myself chasing sources when I need any of
> this. Frankly by now I have already remembered roughly where to look for.
>
> Once tracked down however the description within sources is pretty good
> actually, so please refer there for the time being.
Material for a wiki page?
Ralf
prev parent reply other threads:[~2016-05-20 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:04 [PATCH] MIPS: Fix write_gc0_* macros when writing zero James Hogan
2016-05-18 16:04 ` James Hogan
2016-05-20 8:01 ` Maciej W. Rozycki
2016-05-20 8:01 ` Maciej W. Rozycki
2016-05-20 8:13 ` James Hogan
2016-05-20 8:13 ` James Hogan
2016-05-20 8:31 ` Maciej W. Rozycki
2016-05-20 8:31 ` Maciej W. Rozycki
2016-05-20 13:13 ` Ralf Baechle [this message]
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=20160520131310.GA13016@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@imgtec.com \
/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