From owner-svn-src-projects@FreeBSD.ORG Mon Oct 22 23:18:24 2012 Return-Path: Delivered-To: svn-src-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB90C2E5; Mon, 22 Oct 2012 23:18:24 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9EB608FC18; Mon, 22 Oct 2012 23:18:24 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 55D5011E48; Tue, 23 Oct 2012 09:18:17 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local (c-71-56-248-150.hsd1.co.comcast.net [71.56.248.150]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BHF35722 (AUTH peterg@ptree32.com.au); Tue, 23 Oct 2012 09:18:13 +1000 Message-ID: <5085D433.4020101@freebsd.org> Date: Mon, 22 Oct 2012 17:18:11 -0600 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: Jilles Tjoelker Subject: Re: svn commit: r241744 - projects/bhyve/usr.sbin/bhyve References: <201210191811.q9JIBIQu049356@svn.freebsd.org> <20121021121006.GA96141@stack.nl> In-Reply-To: <20121021121006.GA96141@stack.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Info: RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,SPF_SOFTFAIL X-Junkmail-Status: score=24/51, host=dommail.onthenet.com.au Cc: svn-src-projects@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the src " projects" tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 23:18:25 -0000 > Case 4 looks wrong. A 32-bit write clears the top 32 bits of the > register instead of preserving them. Yep, you're right. How about: > + case 4: > + val = (reg & ~0xffffffffUL) | (operand & 0xffffffffUL); > + break; > I have no idea whether this will actually fix/break anything. Lucky so far but it would be sure to blow up in the future. later, Peter.