From: renzo@cs.unibo.it (Renzo Davoli)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch: Sparc system support
Date: Fri, 1 Oct 2004 16:10:29 +0200 [thread overview]
Message-ID: <20041001141029.GA19335@cs.unibo.it> (raw)
In-Reply-To: <415C874B.6070307@bellard.org>
On Fri, Oct 01, 2004 at 12:23:07AM +0200, Fabrice Bellard wrote:
> I applied your patches with some modifications. Please update your
> sources with the CVS version and tell me if you see problems in my
> modifications.
Yes, I do ;-)
With the latest cvs I get stuck during the compilation inside
sparc-user. (I am working on a linuxppc host)
In file included from
/....... /qemu/translate-all.c:41:
op.h: In function `dyngen_code':
op.h:4781: error: parse error before ')' token
op.h:4782: error: parse error before ')' token
op.h:4797: error: parse error before ')' token
op.h:4798: error: parse error before ')' token
In fact there is something wrong in the op.h file:
Line 4778:
case INDEX_op_fitos: {
extern void op_fitos();
memcpy(gen_code_ptr, (void *)((char *)&op_fitos+0), 56);
*(uint16_t *)(gen_code_ptr + 26) = ((long)(&) + 0 + 0x8000) >> 16;
*(uint16_t *)(gen_code_ptr + 30) = ((long)(&) + 0);
gen_code_ptr += 56;
}
(long)(&) .... the operand is missing.
The same error appears again some lines below:
Line 4794:
case INDEX_op_fitod: {
extern void op_fitod();
memcpy(gen_code_ptr, (void *)((char *)&op_fitod+0), 52);
*(uint16_t *)(gen_code_ptr + 26) = ((long)(&) + 8 + 0x8000) >> 16;
*(uint16_t *)(gen_code_ptr + 30) = ((long)(&) + 8);
gen_code_ptr += 52;
}
ciao
renzo
next prev parent reply other threads:[~2004-10-01 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 16:01 [Qemu-devel] Patch: Sparc system support Blue Swirl
2004-09-30 22:23 ` Fabrice Bellard
2004-10-01 14:10 ` Renzo Davoli [this message]
2004-10-01 16:00 ` Johannes Schindelin
2004-10-01 23:06 ` J. Mayer
2004-10-02 3:50 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2004-10-02 11:07 Blue Swirl
2004-10-02 13:07 ` Fabrice Bellard
2004-10-03 7:37 Blue Swirl
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=20041001141029.GA19335@cs.unibo.it \
--to=renzo@cs.unibo.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.