From: Thiemo Seufer <ths@networkno.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gccism's are ok?
Date: Tue, 12 Aug 2008 10:28:36 +0200 [thread overview]
Message-ID: <20080812082836.GA8445@networkno.de> (raw)
In-Reply-To: <48A03D89.3020005@redhat.com>
Gerd Hoffmann wrote:
> Hi,
>
> Quick question: Is it ok to use gcc-specific features in qemu? Or will
> that break builds on some platform?
>
> Linux obviously is gcc, MacOS X too as far I know. MinGW on Windows is
> gcc too. Anything else we care about?
The dyngen targets still require gcc3 to build, OTOH making qemu more
portable is valuable. I believe the policy should be "avoid compiler
extensions unless it is hard to do without".
> I'm thinking especially about the constructor attribute. That would
> allow to make drivers self-contained, by having a register() call in a
> small constructor function ...
This idea is IMHO of dubious value. It obfuscates the control flow, and
it wouldn't work for a plugin system (where self-containedness would be
the biggest win).
Thiemo
prev parent reply other threads:[~2008-08-12 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 13:24 [Qemu-devel] gccism's are ok? Gerd Hoffmann
2008-08-11 13:38 ` Glauber Costa
2008-08-11 13:53 ` Anthony Liguori
2008-08-11 14:15 ` Johannes Schindelin
2008-08-12 8:28 ` Thiemo Seufer [this message]
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=20080812082836.GA8445@networkno.de \
--to=ths@networkno.de \
--cc=kraxel@redhat.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.