qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: qemu-devel@nongnu.org, "François Revol" <revol@free.fr>
Subject: Re: [Qemu-devel] c99 or not?
Date: Thu, 21 Aug 2008 23:58:05 +0200	[thread overview]
Message-ID: <23611F7C-536F-4BFB-BFED-3ACBA00A08CA@web.de> (raw)
In-Reply-To: <28953775164-BeMail@laptop>


Am 18.08.2008 um 00:33 schrieb François Revol:

> As a BeOS and Haiku dev, I'm used to having to "fix" apps back to c89
> to get them working with gcc2 because we are forced to stick to it due
> to the C++ ABI breackage.
> Haiku shall also provice gcc4 soon, and it might be possible to get
> gcc4 usable under BeOS, but it's like hunting a fly with a hand
> grenade.

It's not just about where variables are declared or how fields are  
initialized, but also some assumptions that cannot safely be made in  
ANSI C (iirc someone from Plan 9 had complained, too). Anyway, a lot  
of code has recently been reworked to consequently use C99 features,  
so reverting those is unlikely to happen.

QEMU doesn't use C++ to my knowledge, so it should work just fine  
across ABIs. Just means you'd currently have to cross-compile for  
Haiku. TCG and the recent addition of a --disable-aio switch for  
OpenBSD should help with that if you want to do it.

> I didn't try to build QEMU on BeOS for quite some time, not even
> sure it'd still build. I don't know if Mickael Lotz (BeOS port
> maintainer IIRC) has recent builds either.

Michael has apparently posted 0.9.1 on BeBits:
http://www.bebits.com/app/4208

Didn't try it though, I rather run BeOS or Haiku as guests. Michael  
said his patches were very intrusive, so he doesn't post them here.

Andreas

  reply	other threads:[~2008-08-21 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 22:22 [Qemu-devel] c99 or not? Ben Taylor
2008-08-17 22:33 ` François Revol
2008-08-21 21:58   ` Andreas Färber [this message]
2008-08-17 23:28 ` Anthony Liguori
2008-08-17 23:34   ` Ben Taylor
2008-08-21 19:43     ` Andreas Färber

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=23611F7C-536F-4BFB-BFED-3ACBA00A08CA@web.de \
    --to=andreas.faerber@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    /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).