From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg-hppa: Implement movcond
Date: Sat, 22 Sep 2012 16:55:14 +0200 [thread overview]
Message-ID: <20120922145514.GA17084@ohm.aurel32.net> (raw)
In-Reply-To: <505DB261.3010809@twiddle.net>
On Sat, Sep 22, 2012 at 05:43:13AM -0700, Richard Henderson wrote:
> On 2012-09-22 03:01, Aurelien Jarno wrote:
> >> > + /* ??? We can actually support a signed 14-bit arg3, but we
> >> > + only have existing constraints for a signed 11-bit. */
> >> > + { INDEX_op_movcond_i32, { "r", "rZ", "rI", "rI", "0" } },
> >> > +
> > What's the problem in adding a constraint for that? The lack of
> > available letters? ;-)
> >
>
> Just a tad more involved than I had time for at the moment.
> Could you go ahead and apply as-is, and I'll get back to
> that some other day?
>
Applied.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2012-09-22 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 1:46 [Qemu-devel] [PATCH] tcg-hppa: Implement movcond Richard Henderson
2012-09-22 10:01 ` Aurelien Jarno
2012-09-22 12:43 ` Richard Henderson
2012-09-22 14:55 ` Aurelien Jarno [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=20120922145514.GA17084@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).