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] [PATCH] Introduce Makefile config fragments for OS-speci

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Introduce Makefile config fragments for OS-specific differences.
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Tue, 17 Oct 2006 16:22:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Oct 2006 08:23:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15AB0B2.2A8F%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <20061017124257.GB4626@xxxxxxxxxxxxxxxxxxxx> <C15AB0B2.2A8F%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Oct 17, 2006 at 04:09:22PM +0100, Keir Fraser wrote:

> > -ifneq ($(debug),y)
> > -# Optimisation flags are overridable
> > -CFLAGS    ?= -O2 -fomit-frame-pointer
> > -CFLAGS    += -DNDEBUG
> > -else
> > -# Less than -O1 produces bad code and large stack frames
> > -CFLAGS    ?= -O1 -fno-omit-frame-pointer
> > -CFLAGS    += -g
> > -endif
> 
> Generally this patch is fine, but does the above chunk have to be made
> OS-specific? Does Solaris specifically have something against
> -fomit-frame-pointer?

Yes, it's a fundamental principle that all the software we deliver can
produce meaningful stack traces.

> Also, moving KERNEL_REPO/KERNELS/XKERNELS seems unnecessary. There are still
> rules consuming those variables in the root Makefile, so leaving
> KERNELS/XKERNELS nearby makes sense to me.

This is specifically to make sure that KERNELS is empty on Solaris.
Otherwise, we have to add some $(XEN_OS) gook to $(XEN_ROOT)/Makefile.
Hopefully these are going away soonish anyway ;)

regards
john

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

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