From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: todays xen-unstable is throwing gcc errors when compiling on PPC
Date: Mon, 09 Jul 2007 15:11:31 -0500 [thread overview]
Message-ID: <1184011891.15329.4.camel@laptop> (raw)
When compiling Xen on PPC today I get the following error that is being
caused by casting (u32 *). Once the cast is removed all is well and
things compile fine. Is this happening on x86 or x86-64 ? I'm using gcc
4.1.0 on Suse SLES 10.
There Error:
grant_table.c: In function ‘gnttab_prepare_for_transfer’:
grant_table.c:825: warning: dereferencing type-punned pointer will break
strict-aliasing rules
grant_table.c: In function ‘__acquire_grant_for_copy’:
grant_table.c:1055: warning: dereferencing type-punned pointer will
break strict-aliasing rules
grant_table.c:1080: warning: dereferencing type-punned pointer will
break strict-aliasing rules
grant_table.c:1080: warning: dereferencing type-punned pointer will
break strict-aliasing rules
grant_table.c:1080: warning: dereferencing type-punned pointer will
break strict-aliasing rules
grant_table.c:1080: warning: dereferencing type-punned pointer will
break strict-aliasing rules
grant_table.c:1080: warning: dereferencing type-punned pointer will
break strict-aliasing rules
make[3]: *** [grant_table.o] Error 1
make[3]: Leaving directory `/Work/xen-unstable.hg/xen/common'
make[2]: *** [/Work/xen-unstable.hg/xen/common/built_in.o] Error 2
make[2]: Leaving directory `/Work/xen-unstable.hg/xen/arch/powerpc'
make[1]: *** [/Work/xen-unstable.hg/xen/xen] Error 2
make[1]: Leaving directory `/Work/xen-unstable.hg/xen'
make: *** [build] Error 2
next reply other threads:[~2007-07-09 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 20:11 Jerone Young [this message]
2007-07-09 21:23 ` todays xen-unstable is throwing gcc errors when compiling on PPC Keir Fraser
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=1184011891.15329.4.camel@laptop \
--to=jyoung5@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ppc-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.