From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NK9qH-0004YU-2d for qemu-devel@nongnu.org; Mon, 14 Dec 2009 07:15:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NK9qC-0004XM-5I for qemu-devel@nongnu.org; Mon, 14 Dec 2009 07:15:56 -0500 Received: from [199.232.76.173] (port=35289 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NK9qB-0004XJ-Uy for qemu-devel@nongnu.org; Mon, 14 Dec 2009 07:15:51 -0500 Received: from mail-pz0-f188.google.com ([209.85.222.188]:39329) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NK9qB-0001WU-Nh for qemu-devel@nongnu.org; Mon, 14 Dec 2009 07:15:51 -0500 Received: by pzk26 with SMTP id 26so2016671pzk.4 for ; Mon, 14 Dec 2009 04:15:50 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <200912141207.22651.paul@codesourcery.com> References: <1260788953-30794-1-git-send-email-nemesisofstate@gmail.com> <200912141207.22651.paul@codesourcery.com> Date: Mon, 14 Dec 2009 13:15:50 +0100 Message-ID: <761ea48b0912140415i5d78ddf8h8975aa39b4aee00d@mail.gmail.com> Subject: Re: [Qemu-devel] [PATCH] correcting ARM CPSR register bit position comment From: Laurent Desnogues Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: nemesisofstate Cc: qemu-devel@nongnu.org On Mon, Dec 14, 2009 at 1:07 PM, Paul Brook wrote: >> - =A0 =A0uint32_t VF; /* V is the bit 31. All other bits are undefined *= / >> + =A0 =A0uint32_t VF; /* V is the bit 28. */ > > No. The original comment is correct. And so that the answer is at least a bit useful: these fields are not directly mapped to CPSR; they are the results of computations and can then be translated to bits in CPSR (look for cpsr_read/cpsr_write in helper.c). If you want to see how VF is set, look for add_cc in op_helper.c. This is done this way to speed up simulation. HTH, Laurent