From: Jamie Lokier <jamie@shareable.org>
To: dfeustel@mindspring.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Many syntax errors in op.h
Date: Tue, 15 Nov 2005 17:23:20 +0000 [thread overview]
Message-ID: <20051115172320.GC4959@mail.shareable.org> (raw)
In-Reply-To: <200511150950.20856.dfeustel@verizon.net>
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)(&) + 14;
>
> generate syntax errors (apparently because of the use of "(&)")
> with the c compiler used in OpenBSD 3.7 (gcc (GCC) 3.3.5 (propolice)).
"(&)" is not valid C.
> Similar statements with a symbol following the "&" (eg "(&xyz)") do
> not generate syntax errors.
Because that is valid C.
-- Jamie
next prev parent reply other threads:[~2005-11-15 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 14:50 [Qemu-devel] Many syntax errors in op.h Dave Feustel
2005-11-15 15:43 ` Paul Brook
2005-11-15 17:17 ` Johannes Schindelin
2005-11-15 17:23 ` Jamie Lokier [this message]
2005-11-15 18:05 ` Dave Feustel
2005-11-15 18:30 ` Johannes Schindelin
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=20051115172320.GC4959@mail.shareable.org \
--to=jamie@shareable.org \
--cc=dfeustel@mindspring.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 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.