From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CAbHX-0003vT-G7 for qemu-devel@nongnu.org; Thu, 23 Sep 2004 17:37:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CAbHV-0003vG-U9 for qemu-devel@nongnu.org; Thu, 23 Sep 2004 17:37:39 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CAbHV-0003vD-Q8 for qemu-devel@nongnu.org; Thu, 23 Sep 2004 17:37:37 -0400 Received: from [62.241.160.73] (helo=colossus.systems.pipex.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CAbAz-0007wG-PY for qemu-devel@nongnu.org; Thu, 23 Sep 2004 17:30:53 -0400 From: Paul Brook Subject: Re: [Qemu-devel] AMD64 Gentoo needs help Date: Thu, 23 Sep 2004 22:30:44 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409232230.44451.paul@codesourcery.com> 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 On Thursday 23 September 2004 21:21, Martin Garton wrote: > On Thu, 23 Sep 2004, jmf wrote: > > I treid that and before the segfault below happen, now a black window > > appears and dissappears very quickly > > I believe the problem is that qemu is not 64bit clean code because it does > things like casting from pointers to ints and back which is okay when they > are the same size (ie, on x86) but not when a pointer is twice as long as > an int (ie, on amd64) You will have seen warnings about this when > compiling. Doesn't Gentoo use gcc3.4? If so I'd guess it's more likely that this is the problem. gcc3.4 performs optimizations that break assumptions in the dyngen code. Paul