From: Peter Maydell <peter.maydell@linaro.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] w32: Add macro timersub to sys/time.h
Date: Sat, 5 Mar 2011 09:55:51 +0000 [thread overview]
Message-ID: <AANLkTin5fkJv_dmUFKbFysZoYWSKA9NowRa8P5fYmUU_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimB53SW2y=F5qXcrka1qa0HOJ4Z3_KkfGUMH2=y@mail.gmail.com>
On 5 March 2011 09:48, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Sat, Mar 5, 2011 at 11:42 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 5 March 2011 09:34, Blue Swirl <blauwirbel@gmail.com> wrote:
>>> On Sun, Feb 27, 2011 at 7:52 PM, Stefan Weil <weil@mail.berlios.de> wrote:
>>>> +#include_next <sys/time.h>
>>>
>>> Isn't include_next an extension by GCC?
>>
>> Are gcc extensions forbidden? We already have plenty of
>> code that uses gcc-specific syntax or gcc extensions...
>
> No, but relying on them is not OK. For example gcc attributes are
> wrapped in macros to allow other implementations.
Three random counter-examples:
vl.c:
machine->max_cpus = machine->max_cpus ?: 1; /* Default to UP */
That use of ?: is a gcc extension.
target-i386/cpu.h:
register struct CPUX86State *env asm(AREG0);
Explicit register variables are a gcc extension.
qemu-timer-common.c:
static void __attribute__((constructor)) init_get_clock(void)
gcc-specific attribute not hidden by a macro.
-- PMM
next prev parent reply other threads:[~2011-03-05 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 17:52 [Qemu-devel] [PATCH 1/3] w32: Add new directory hierarchy for MinGW extensions Stefan Weil
2011-02-27 17:52 ` [Qemu-devel] [PATCH 2/3] w32: Add macro timersub to sys/time.h Stefan Weil
2011-03-05 9:34 ` Blue Swirl
2011-03-05 9:42 ` Peter Maydell
2011-03-05 9:48 ` Blue Swirl
2011-03-05 9:55 ` Peter Maydell [this message]
2011-03-05 10:31 ` Blue Swirl
2011-03-06 22:15 ` Stefan Weil
2011-02-27 17:52 ` [Qemu-devel] [PATCH 3/3] osdep: Remove conditional compilation (fixes w32 compilation) Stefan Weil
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=AANLkTin5fkJv_dmUFKbFysZoYWSKA9NowRa8P5fYmUU_@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.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).