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

RE: [Xen-ia64-devel] [Patch] tools build patch for gcc3.4


  • To: <takebe_akio@xxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 17 Nov 2005 06:20:53 -0800
  • Delivery-date: Thu, 17 Nov 2005 14:21:21 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXre6OZKEg3JkAaR/GHi14bBhxqMAABhQ/w
  • Thread-topic: [Xen-ia64-devel] [Patch] tools build patch for gcc3.4

Is there a cleaner way of doing this?   This is a common
file (shared with Xen/x86) and I don't think Keir will like
this patch.  Why is __ASSEMBLY__ turned on?  (it should only
be turned on when compiling assembly code)  And why do
__IA64_UL and __IA64_UL_CONST need to be redefined?

Thanks,
Dan

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of takebe_akio@xxxxxxxxxxxxxx
> Sent: Thursday, November 17, 2005 6:33 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] [Patch] tools build patch for gcc3.4
> 
> Hi,
> 
> I and Kanno made a tools build patch for gcc3.4.
> I test it work on RHEL4 and Xen.
> I confirmed to be able to compile tools on RHEL3,
> but still don't test it works on RHEL3 and Xen.
> 
> Signed-off-by Akio Takabe <takebe_akio@xxxxxxxxxxxxxx>
> Signed-off-by Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
> 
> Best Regards,
> 
> Akio Takebe 
> 

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


 


Rackspace

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