From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:57279)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1TFP39-0007g4-7n
	for qemu-devel@nongnu.org; Sat, 22 Sep 2012 08:43:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1TFP38-0007GQ-AO
	for qemu-devel@nongnu.org; Sat, 22 Sep 2012 08:43:11 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:38324)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1TFP38-0007GM-4Q
	for qemu-devel@nongnu.org; Sat, 22 Sep 2012 08:43:10 -0400
Received: by pbbrp12 with SMTP id rp12so9577988pbb.4
	for <qemu-devel@nongnu.org>; Sat, 22 Sep 2012 05:43:09 -0700 (PDT)
Sender: Richard Henderson <rth7680@gmail.com>
Message-ID: <505DB261.3010809@twiddle.net>
Date: Sat, 22 Sep 2012 05:43:13 -0700
From: Richard Henderson <rth@twiddle.net>
MIME-Version: 1.0
References: <1348278392-3075-1-git-send-email-rth@twiddle.net>
	<20120922100107.GG29951@hall.aurel32.net>
In-Reply-To: <20120922100107.GG29951@hall.aurel32.net>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] tcg-hppa: Implement movcond
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org

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?


r~