From: Jerone Young <jyoung5@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] make shadow code compile ok on FC4 which is using gcc4
Date: Mon, 11 Jul 2005 15:11:49 -0500 [thread overview]
Message-ID: <1121112710.8028.16.camel@thinkpad> (raw)
In-Reply-To: <b8debd4915ff69e3dc7ca4d4fc35e240@cl.cam.ac.uk>
On Mon, 2005-07-11 at 20:58 +0100, Keir Fraser wrote:
> On 11 Jul 2005, at 20:19, David Hopwood wrote:
>
> >> We need this patch to make shadow code compile ok on FC4 which is
> >> using
> >> gcc4.
> >
> > Given gcc4's propensity to warn about things that are often harmless,
> > is it
> > still a good idea to be compiling with -Werror?
>
> It's been slightly annoying but not too much of a pain to keep things
> working with gcc4, and using -Werror does mean that genuine warnings
> don't get lost in the noise.
>
> Anyway, we have more serious problems with gcc4 (I can't boot dom0 as
> far as a login prompt when I build xen+xenlinux with gcc4). Currently
> gcc 3.2.x and 3.3.x are the main supported compilers.
That's odd. I'm booting and running xen+xenlinux fine with gcc4 under
FC4...with the 2.6.12 patch ...under x86-64 no less.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
next prev parent reply other threads:[~2005-07-11 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 14:35 [PATCH] make shadow code compile ok on FC4 which is using gcc4 Li, Xin B
2005-07-11 19:19 ` David Hopwood
2005-07-11 19:58 ` Keir Fraser
2005-07-11 20:11 ` Jerone Young [this message]
2005-07-11 20:15 ` Keir Fraser
2005-07-11 20:01 ` Rik van Riel
2005-07-11 23:32 ` David Hopwood
2005-07-12 2:29 ` Rik van Riel
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=1121112710.8028.16.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.