From: Herbert Poetzl <herbert@13thfloor.at>
To: Jens Arm <Jens.Arm@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hand written code generator #2
Date: Wed, 1 Jun 2005 11:53:59 +0200 [thread overview]
Message-ID: <20050601095359.GB13111@MAIL.13thfloor.at> (raw)
In-Reply-To: <20050601074033.06b81f62.Jens.Arm@gmx.de>
On Wed, Jun 01, 2005 at 07:40:33AM +0200, Jens Arm wrote:
> Hi Paul
>
> I get a compile errorif I try with latest qemu cvs:
>
> ../dyngen -o op.h op.o
> ../dyngen -c -o opc.h op.o
> gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/tux/tmp/qemu/target-sparc -I/home/tux/tmp/qemu -I/home/tux/tmp/qemu/host-i386 -I/home/tux/tmp/qemu/linux-user -I/home/tux/tmp/qemu/linux-user/sparc -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/tux/tmp/qemu/fpu -I/home/tux/tmp/qemu/slirp -c -o translate-op.o /home/tux/tmp/qemu/translate-op.c
> make[1]: *** Keine Regel vorhanden, um das Target »qregs.def«,
> benötigt von »translate-qop.o«, zu erstellen. Schluss.
> make[1]: Leaving directory `/home/tux/tmp/qemu/sparc-user'
> make: *** [all] Fehler 1
if you are more comfortable with a localized error message,
that's probably fine, but for postings to an english spoken
ml you should really use LANG=C LC_ALL=C ....
best,
Herbert
> Jens
>
> On Tue, 31 May 2005 16:23:28 +0100
> Paul Brook <paul@codesourcery.com> wrote:
>
> > I've made available a new version of my hand-written code generator for qemu.
> > The patch is getting rather large, so I've put it on a web server to avoid
> > spamming the list:
> > https://nowt.dyndns.org/patch.qemu_qop.gz
> >
> > In principle it's very similar to the previous patch. The main difference is
> > that it now supports all target architectures, including 64-bit targets.
> >
> > The i386 changes have been tested by booting knoppix and win2k and win98.
> > x86-64 tested by booting a debian amd64 install cd.
> > ppc chanages tested by booting a debina install cd and running nbench under
> > ppc-user.
> > My sparc debian cd doesn't boot under qemu (stops responding just after
> > loading the kernel). Does anyone have any images I could use for testing
> > sparc emulation?
> >
> > To support 64-bit targets each qreg now has a "mode" which determines its
> > size. 64-bit qregs can be implemented using pairs of host registers on 32-bit
> > hosts, or single registers on 64-bit hosts.
> >
> > ppc and sparc targets only have nominal support. I've done the bare minimum
> > needed to make them work. Arm is still the only target that really takes
> > advantage of any of the new functionality.
> >
> > Next on my todo list is support for ppc and x86-64 hosts.
> >
> > Paul
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2005-06-01 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 15:23 [Qemu-devel] Hand written code generator #2 Paul Brook
2005-06-01 5:40 ` Jens Arm
2005-06-01 9:53 ` Herbert Poetzl [this message]
2005-06-01 12:36 ` Paul Brook
2005-06-02 10:53 ` Christian MICHON
2005-06-02 13:31 ` Paul Brook
2005-06-02 13:36 ` Christian MICHON
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=20050601095359.GB13111@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=Jens.Arm@gmx.de \
--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).