This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1186] New: xen ia64 build failure using gcc-4.3

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1186] New: xen ia64 build failure using gcc-4.3
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 5 Mar 2008 15:12:55 -0800
Delivery-date: Wed, 05 Mar 2008 15:13:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           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-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: doug.chapman@xxxxxx

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;

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>