From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1J6xgK-0007N3-AS
	for qemu-devel@nongnu.org; Mon, 24 Dec 2007 19:30:04 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1J6xgH-0007KO-VR
	for qemu-devel@nongnu.org; Mon, 24 Dec 2007 19:30:04 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1J6xgH-0007KL-OC
	for qemu-devel@nongnu.org; Mon, 24 Dec 2007 19:30:01 -0500
Received: from relay01.mx.bawue.net ([193.7.176.67])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <ths@networkno.de>) id 1J6xgH-00051E-ID
	for qemu-devel@nongnu.org; Mon, 24 Dec 2007 19:30:01 -0500
Date: Tue, 25 Dec 2007 00:29:56 +0000
From: Thiemo Seufer <ths@networkno.de>
Subject: Re: [Qemu-devel] qemu on alpha
Message-ID: <20071225002955.GB5128@networkno.de>
References: <691343.68402.qm@web53703.mail.re2.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <691343.68402.qm@web53703.mail.re2.yahoo.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gabriele Gorla <gorlik@yahoo.com>
Cc: qemu-devel@nongnu.org

Gabriele Gorla wrote:
> Hello,
> I recently downloaded qemu-0.9.0 and tried to compile
> it on alpha.
> I was not able to get any target to compile.
> 
> I searched the mailing list but I was not able to find
> any recent information on the alpha host status.
> 
> I am using gcc-3.3.6 on debian stable with upgraded
> kernel
> 2.6.22
> I have tried with gcc-3.4 and 4.1 with similar
> results.
> 
> I patched the line:
> #if defined (__x86_64__) || defined(__ia64) ||
> defined(__alpha__)
> of file dyngen-exec.h to add the alpha to the 64-bit
> architectures to prevent redefinition of int64_t and
> uint64_t 
> 
> beside tons of warning about casting pointers to int
> of different sizes I get the following two fatal
> errors:
> 
> qemu-0.9.0/target-i386/ops_template.h:278: warning:
> implicit declaration of function `GOTO_LABEL_PARAM'
> 
> qemu-0.9.0/target-i386/translate.c:1898: error: too
> many arguments to function `gen_op_jnz_T0_label'
> qemu-0.9.0/target-i386/translate.c:1900: error: too
> many arguments to function `gen_op_jmp_label'
> 
> in the translate.c file the function is called with:
>         gen_op_jmp_label(l2);
> 
> but in gen-op.h it is defined as:
> static inline void gen_op_jmp_label(void)
> {
>     *gen_opc_ptr++ = INDEX_op_jmp_label;
> }
> 
> same for gen_op_jnz_T0_label
> 
> 
> for GOTO_LABEL_PARAM the definition is completely
> missing from dyngen-exec.h (it is there for all other
> host CPUs except m68k)
> 
> Unfortunately my understanding of the code is not
> sufficient to do anything useful at this point.
> I would really appreciate if someone could give me a
> hint.

Current CVS has probably less broken alpha host support. Still, it is
unlikely to work out of the box, fixing this requires some knowledge
of alpha assembler. (E.g. for implementing a GOTO_LABEL_PARAM for alpha.)


Thiemo