WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: c/s 14420 (gcc 3.4+ required)

To: Jan Beulich <jbeulich@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: c/s 14420 (gcc 3.4+ required)
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Mon, 19 Mar 2007 13:22:33 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 19 Mar 2007 06:21:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45FE93DB.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdqKabr5Y/x79YcEduRVQAX8io7RQ==
Thread-topic: [Xen-devel] Re: c/s 14420 (gcc 3.4+ required)
User-agent: Microsoft-Entourage/11.2.5.060620
On 19/3/07 12:44, "Jan Beulich" <jbeulich@xxxxxxxxxx> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>