qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] gccism's are ok?
Date: Mon, 11 Aug 2008 15:24:25 +0200	[thread overview]
Message-ID: <48A03D89.3020005@redhat.com> (raw)

  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?

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 ...

cheers,
  Gerd

-- 
http://kraxel.fedorapeople.org/xenner/

             reply	other threads:[~2008-08-11 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 13:24 Gerd Hoffmann [this message]
2008-08-11 13:38 ` [Qemu-devel] gccism's are ok? Glauber Costa
2008-08-11 13:53 ` Anthony Liguori
2008-08-11 14:15   ` Johannes Schindelin
2008-08-12  8:28 ` Thiemo Seufer

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=48A03D89.3020005@redhat.com \
    --to=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 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).