Re: [Qemu-devel] ColdFire/m68k target

[Neo Jia]

Paul,

I just checkout from CVS repository and encountered the following problem while building the code.

It seems you eleminate your original arguments of function gen_op_divs and gen_op_divu.

Could you take a look?

gcc -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k -I/home/cjia/research/Operating_Systems/qemu_cvs -I/home/cjia/research/Operating_Systems/qemu_cvs/linux-user -I/home/cjia/research/Operating_Systems/qemu_cvs/linux-user/m68k -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/cjia/research/Operating_Systems/qemu_cvs/fpu -I/home/cjia/research/Operating_Systems/qemu_cvs/slirp -c -o 
translate.o /home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c: In function `disas_divw':
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c:717: error: too many arguments to function `gen_op_divs'
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c:719: error: too many arguments to function `gen_op_divu'
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c: In function `disas_divl':
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c:750: error: too many arguments to function `gen_op_divs'
/home/cjia/research/Operating_Systems/qemu_cvs/target-m68k/translate.c:752: error: too many arguments to function `gen_op_divu'
make[1]: *** [translate.o] Error 1
make[1]: Leaving directory `/home/cjia/research/Operating_Systems/qemu_cvs/m68k-user'
make: *** [subdir-m68k-user] Error 2

Thanks,
Neo

On 10/21/06, Paul Brook <address@hidden> wrote:

I've just committed ColdFire/M68K target support to cvs. This implements
usermode emulation for ColdFire CPUs, including the FPU. The CPU emulation
has been reasonably well tested, but linux syscall emulation only lightly
tested.

For those that don't know, ColdFire is a subset of the old m68k architecture,
with a few minor differences, and a slightly different FPU.

I'll probably be implementing full system emulation sometime (Freescale
M5xxxEVB dev board).

M68k code will not run on the current emulation. Implementing the missing 68k
bits (addressing modes and bitfield instructions) probably wouldn't be that
hard. Implementing 68881 FPU emulation is a bit harder 'cos it
uses "extended" precision registers.

The code is a bit different to most other qemu targets because I originally
wrote it for my code generation backend rather than dyngen. The main
translation code is unmodified, with glue to make it work with dyngen. For
this reason the generated code isn't as efficient as it could be.

Paul

P.S.
Anyone wanting to play with ColdFire emulation can find toolchains at
http://www.codesourcery.com/gnu_toolchains/coldfire/index_html


_______________________________________________
Qemu-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/qemu-devel

-- 
I would remember that if researchers were not ambitious 
probably today we haven't the technology we are using!