From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: c/s 14420 (gcc 3.4+ required) Date: Mon, 19 Mar 2007 13:22:33 +0000 Message-ID: References: <45FE93DB.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45FE93DB.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 19/3/07 12:44, "Jan Beulich" 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