From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KxLmb-0003nV-J6 for qemu-devel@nongnu.org; Tue, 04 Nov 2008 08:17:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KxLmb-0003n8-0P for qemu-devel@nongnu.org; Tue, 04 Nov 2008 08:17:21 -0500 Received: from [199.232.76.173] (port=56498 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KxLma-0003n0-Qj for qemu-devel@nongnu.org; Tue, 04 Nov 2008 08:17:20 -0500 Received: from savannah.gnu.org ([199.232.41.3]:49398 helo=sv.gnu.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KxLma-0005nH-8P for qemu-devel@nongnu.org; Tue, 04 Nov 2008 08:17:20 -0500 Received: from cvs.savannah.gnu.org ([199.232.41.69]) by sv.gnu.org with esmtp (Exim 4.63) (envelope-from ) id 1KxLmZ-0005OV-8h for qemu-devel@nongnu.org; Tue, 04 Nov 2008 13:17:19 +0000 Received: from pbrook by cvs.savannah.gnu.org with local (Exim 4.63) (envelope-from ) id 1KxLmY-0005OP-KL for qemu-devel@nongnu.org; Tue, 04 Nov 2008 13:17:18 +0000 MIME-Version: 1.0 Errors-To: pbrook Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Paul Brook Message-Id: Date: Tue, 04 Nov 2008 13:17:18 +0000 Subject: [Qemu-devel] [5619] Mention output overlaps. Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Revision: 5619 http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5619 Author: pbrook Date: 2008-11-04 13:17:17 +0000 (Tue, 04 Nov 2008) Log Message: ----------- Mention output overlaps. Modified Paths: -------------- trunk/tcg/README Modified: trunk/tcg/README =================================================================== --- trunk/tcg/README 2008-11-04 12:33:21 UTC (rev 5618) +++ trunk/tcg/README 2008-11-04 13:17:17 UTC (rev 5619) @@ -390,6 +390,11 @@ instruction. Memory constraints are not supported in this version. Aliases are specified in the input operands as for GCC. +The same register may be used for both an input and an output, even when +they are not explicitly aliased. If an op expands to multiple target +instructions then care must be taken to avoid clobbering input values. +GCC style "early clobber" outputs are not currently supported. + A target can define specific register or constant constraints. If an operation uses a constant input constraint which does not allow all constants, it must also accept registers in order to have a fallback.