All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [ANNOUNCE] First release candidates for Xen 4.0.4 and 4.1.3
Date: Wed, 9 May 2012 20:10:39 +0100	[thread overview]
Message-ID: <4FAAC12F.8010507@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205091956510.14172@vega-c.dur.ac.uk>

On 09/05/12 20:03, M A Young wrote:
> On Tue, 8 May 2012, Keir Fraser wrote:
>
>> Thanks. The same appears to be true in xen-unstable also. Is the solution to
>> simply remove -O0 from the command line? We can test that out in
>> xen-unstable if so, and backport if it causes no problems.
> I got it to build with the attached patch -
> http://koji.fedoraproject.org/koji/taskinfo?taskID=4063767 .
>
> It seems the -O0 option was masking some other compile issues so I had to 
> add -Wno-error=unused-result -Wno-error=array-bounds as well though I 
> imagine the right solution would be to fix the code so it doesn't give 
> warnings (if they haven't already been fixed in xen-unstable).
>
>  	Michael Young

If it is failing -Warray-bounds then the source code probably needs fixing.

Do you have a log of the failures caused by -Warray-bounds ?

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-05-09 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 12:58 [ANNOUNCE] First release candidates for Xen 4.0.4 and 4.1.3 Keir Fraser
2012-05-07 17:18 ` Pavel Matěja
2012-05-07 20:03   ` Keir Fraser
2012-05-07 20:08 ` Andrew Cooper
2012-05-07 20:52 ` M A Young
2012-05-08  7:50   ` Keir Fraser
2012-05-09 19:03     ` M A Young
2012-05-09 19:10       ` Andrew Cooper [this message]
2012-05-09 20:30         ` Olaf Hering
2012-05-11 15:51 ` Olaf Hering
2012-05-14 10:09   ` Jan Beulich

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=4FAAC12F.8010507@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.