Hi,
On Tue, 15 Nov 2005, Dave Feustel wrote:
> On Tuesday 15 November 2005 12:23, Jamie Lokier wrote:
> >
> > "(&)" is not valid C.
>
> That's what I thought too. "&" requires an operand. So why are these
> lines of code in op.h? Should they be commented out? Should a dummy
> operand be inser
On Tuesday 15 November 2005 12:23, Jamie Lokier wrote:
> Dave Feustel wrote:
> > I am making progress as I modify the Qemu source code to work
> > around a number of OpenBSD deficiencies. I don't yet know how
> > to fix the following problem which occurs about 25 times in op.h:
> >
> > C statemen
Dave Feustel wrote:
> I am making progress as I modify the Qemu source code to work
> around a number of OpenBSD deficiencies. I don't yet know how
> to fix the following problem which occurs about 25 times in op.h:
>
> C statements of the form
>
>*(uint32_t *)(gen_code_ptr + 210) = (long)(&
Hi,
On Tue, 15 Nov 2005, Dave Feustel wrote:
>*(uint32_t *)(gen_code_ptr + 210) = (long)(&) + 14;
This is usually a problem with dyngen extracting meaningless relocations
from the object file.
It happened to me when I was working on the MIPS (host) support, and a lot
of these relocations
On Tuesday 15 November 2005 14:50, Dave Feustel wrote:
> I am making progress as I modify the Qemu source code to work
> around a number of OpenBSD deficiencies. I don't yet know how
> to fix the following problem which occurs about 25 times in op.h:
>
> C statements of the form
>
>*(uint32_t *
I am making progress as I modify the Qemu source code to work
around a number of OpenBSD deficiencies. I don't yet know how
to fix the following problem which occurs about 25 times in op.h:
C statements of the form
*(uint32_t *)(gen_code_ptr + 210) = (long)(&) + 14;
generate syntax errors (a
