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


Re: [Xen-ia64-devel] Mini-OS registers and libgcc

To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-ia64-devel] Mini-OS registers and libgcc
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 13 Feb 2008 11:53:59 +0100
Delivery-date: Wed, 13 Feb 2008 03:10:25 -0800
Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:Received:Received: From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding: Content-Disposition:Message-Id; b=jNa8WOXmPTG2704uumobWvJ7zDBUrXDuzGCdkvGBnC71WwixjloOb67Y eAycinNE1DuSNG05fQbR753Dcd1edERytZznT7jMXp5hn6ynhKanVvhQR X6+AzJ7RU4t8Jfk;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080212141219.GA4336@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080212141219.GA4336@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 20070904.708012)
Hi Samuel,

Am Dienstag, 12. Februar 2008 schrieb Samuel Thibault:
> Hello,
> Is there a reason for using -mfixed-range=f2-f5,f12-f15,f32-f127
> when compiling Mini-OS?  Is it really needed since it doesn't
> have a user-land? (though I guess some support would be needed in
> switch_context for instance)

To handle this in a clean way the trap_frame has to be expanded and some fp 
registers have to stored/restored in trap handling.

> Then, are there other reasons for using __*div/di*.S instead of just
> linking with libgcc?

It's possible to use libgcc.a but the flag -mconstant-gp has to be removed 
from the mini-os makefiles and a clean way to add libgcc.a is needed.

> Samuel

By the way current mini-os crashed with Unaligned Reference. 
A small change is needed:
 static void maybe_split(struct xmalloc_hdr *hdr, size_t size, size_t block)
     struct xmalloc_hdr *extra;
-    size_t leftover = block - size;
+    size_t leftover;
+#if defined(__ia64__)
+    size = (size +7 ) & ~7;  /* alignment needed on 8 byte boundary. */
+    leftover = block - size;


Xen-ia64-devel mailing list

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