From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com
Cc: andreas.faerber@web.de, jes@sgi.com
Subject: Re: [Qemu-devel] [patch 1/2] machine struct - use C99 initializers
Date: Mon, 06 Oct 2008 17:38:22 -0600 (MDT) [thread overview]
Message-ID: <20081006.173822.-1749749577.imp@bsdimp.com> (raw)
In-Reply-To: <200810070007.59487.paul@codesourcery.com>
In message: <200810070007.59487.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
: > > 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.
You assume that all upgrades are a good thing. There are often
serious regressions in newer software, especially in not Intel
platforms, that makes it much harder to upgrade and have a working
system afterwards.
I'm saying there needs to be a balance between the latest and
greatest, and known working software...
Warner
next prev parent reply other threads:[~2008-10-06 23:40 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
2008-10-06 23:38 ` M. Warner Losh [this message]
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=20081006.173822.-1749749577.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=andreas.faerber@web.de \
--cc=jes@sgi.com \
--cc=paul@codesourcery.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).