5 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 1186] New: xen ia64 b...
FromSent OnAttachments
bugz...@lists.xensource.com05 Mar 2008 15:12 
bugz...@lists.xensource.com05 Mar 2008 15:14 
bugz...@lists.xensource.com10 Mar 2008 02:46 
bugz...@lists.xensource.com10 Mar 2008 07:48 
bugz...@lists.xensource.com10 Mar 2008 15:42 
Subject:[Xen-bugs] [Bug 1186] New: xen ia64 build failure using gcc-4.3
From:bugz...@lists.xensource.com (bugz@lists.xensource.com)
Date:03/05/2008 03:12:32 PM
List:com.xensource.lists.xen-bugs

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1186

Summary: xen ia64 build failure using gcc-4.3 Product: Xen Version: unstable Platform: IA64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Tools AssignedTo: xen-@lists.xensource.com ReportedBy: doug@hp.com

This fails to build under gcc-4.3 but looking at the code it might have been causing some sort of strange problems before even when it did build since it is writing off the end of an array.

Since Fedora has moved to gcc-4.3 this prevents building this under Fedora-ia64. Also, other tools have dependencies on the xen tools so there are other key things in fedora that break on ia64 because of this.

cc1: warnings being treated as errors ia64/xc_ia64_stubs.c: In function 'xc_ia64_p2m_map': ia64/xc_ia64_stubs.c:95: error: array subscript is above array bounds

The type privcmd_hypercall_t is defined as: typedef struct privcmd_hypercall { __u64 op; __u64 arg[5]; } privcmd_hypercall_t;

but we write 6 items (with the 6th being a zero):

hypercall.op = __HYPERVISOR_ia64_dom0vp_op; hypercall.arg[0] = IA64_DOM0VP_expose_foreign_p2m; hypercall.arg[1] = (unsigned long)addr; hypercall.arg[2] = dom; hypercall.arg[3] = (unsigned long)memmap_info; hypercall.arg[4] = flags; hypercall.arg[5] = 0;