From: "Neo Jia" <neojia@gmail.com>
To: paul@codesourcery.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ColdFire/m68k target
Date: Tue, 31 Oct 2006 14:20:26 -0600 [thread overview]
Message-ID: <5d649bdb0610311220vc802054q9ec008f95259bbb7@mail.gmail.com> (raw)
In-Reply-To: <200610220144.22013.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]
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 <paul@codesourcery.com> 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
> Qemu-devel@nongnu.org
> 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!
[-- Attachment #2: Type: text/html, Size: 3778 bytes --]
next prev parent reply other threads:[~2006-10-31 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 0:44 [Qemu-devel] ColdFire/m68k target Paul Brook
2006-10-31 20:20 ` Neo Jia [this message]
2006-10-31 20:32 ` Paul Brook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d649bdb0610311220vc802054q9ec008f95259bbb7@mail.gmail.com \
--to=neojia@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).