From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>, "Jes Sorensen" <jes@sgi.com>
Subject: Re: [Qemu-devel] [patch 1/2] machine struct - use C99 initializers
Date: Tue, 7 Oct 2008 00:07:58 +0100 [thread overview]
Message-ID: <200810070007.59487.paul@codesourcery.com> (raw)
In-Reply-To: <DD005F45-C3A4-4D89-818A-3FDDFDC29AE1@web.de>
> > GCC is sufficiently C99 compliant to handle this style of
> > initializers.
> > Maybe it's not C99 compliant enough for other stuff, but on this front
> > it does just fine.
>
> You're missing the point: GCC today is not necessarily GCC 4.3+ or
> whatever has just been released these days and included in your
> favorite Linux distro. Just like Sun continues to ship GCC 3.4.3 on
> their latest OpenSolaris builds, the BeOS world and therefore its
> successor(s) are stuck with GCC 2.95.3 due to C++ ABI breakage in
> between major GCC versions. GCC 2 was originally released in '98 iirc
> and hence not C99 compliant. I'd expect your IRIX to face a similar
> issue, at EOL.
If a host system hasn't bothered upgrading their toolchain in 10 years then I
refuse to care. If you really want to run and ancient obsolete OS you should
expect to run equally ancient software.
Paul
next prev parent reply other threads:[~2008-10-06 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:09 [Qemu-devel] [patch 1/2] machine struct - use C99 initializers Jes Sorensen
2008-10-06 15:05 ` Johannes Schindelin
2008-10-06 15:03 ` Jes Sorensen
2008-10-06 15:26 ` Johannes Schindelin
2008-10-06 15:23 ` Anthony Liguori
2008-10-06 20:22 ` Ronan Keryell
2008-10-06 22:46 ` Andreas Färber
2008-10-06 23:07 ` Paul Brook [this message]
2008-10-06 23:38 ` M. Warner Losh
2008-10-07 13:50 ` Paul Brook
2008-10-07 7:13 ` Jes Sorensen
2008-10-26 15:17 ` Andreas Färber
2008-10-06 15:30 ` Thiemo Seufer
2008-10-07 20:34 ` Anthony Liguori
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=200810070007.59487.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=andreas.faerber@web.de \
--cc=jes@sgi.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.