From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: c/s 14420 (gcc 3.4+ required)
Date: Mon, 19 Mar 2007 13:22:33 +0000 [thread overview]
Message-ID: <C2243F19.BCCB%keir@xensource.com> (raw)
In-Reply-To: <45FE93DB.76E4.0078.0@novell.com>
On 19/3/07 12:44, "Jan Beulich" <jbeulich@novell.com> wrote:
>> I just scanned the tree and couldn't spot any such instance. Could you point
>> me to one?
>
> Okay, sorry, I found one - I had skipped the public headers, as I assumed you
> wouldn't change those, forgetting about the few __XEN__/__XEN_TOOLS__
> conditionals in there.
Like I said, its hardly an insurmountable obstacle to support of gcc 3.3.x.
But in general requiring a modern gcc will avoid exposure to bugs specific
to older gcc, avoid needing workarounds for bugs in older gcc, and allow us
to use new gcc features without requiring consideration of older gcc. That's
my default position unless there's a good reason to do otherwise. Given how
much we depend on subtleties of gcc, I think this is the sane approach. :-)
-- Keir
prev parent reply other threads:[~2007-03-19 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 9:35 c/s 14420 (gcc 3.4+ required) Jan Beulich
2007-03-19 9:51 ` Keir Fraser
2007-03-19 12:36 ` Jan Beulich
2007-03-19 12:44 ` Jan Beulich
2007-03-19 13:22 ` Keir Fraser [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=C2243F19.BCCB%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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.