[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Build errors with latest xen-unstable from staging


  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
  • Date: Mon, 07 Feb 2011 08:48:10 -0500
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 07 Feb 2011 05:50:00 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=NT1Jngs9jN7m+VIvikZw7kNHUyXU+e4pzcL/BK+PLJtpbOHR2RvC28N6ZBXMI8MVMr VWLAugcewqjCLrKp+FoY/6sWBehC2URHbIAwnc7LUimbXnTQL8DHric2Mlkok1qBnm/d 6KBaCgcTUFr9VJCzXhElO5eVPjrgStmpF8fcE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Ian Campbell wrote:
> On Sun, 2011-02-06 at 19:01 +0000, Kamala Narasimhan wrote:
> In the Linux kernel they have a macro to annotate such instances:
>         /*
>          * A trick to suppress uninitialized variable warning without 
> generating any
>          * code
>          */
>         #define uninitialized_var(x) x = x
>         
> Do we want something similar?
> 
But why obfuscate a warning that is there for a good reason in most cases?
Aren't we better off initializing the variable or use a compiler option to
suppress it if we must?

Kamala



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.