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

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

To: Xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Tue, 12 Feb 2008 14:12:19 +0000
Delivery-date: Tue, 12 Feb 2008 06:13:17 -0800
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>

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)

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

Samuel

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

Follow-Ups:
- Re: [Xen-ia64-devel] Mini-OS registers and libgcc
  - From: Dietmar Hahn

Prev by Date: [Xen-ia64-devel] Self IOEMUlator: a firmware
Next by Date: RE: [Xen-ia64-devel] Question about migration
Previous by thread: [Xen-ia64-devel] Self IOEMUlator: a firmware
Next by thread: Re: [Xen-ia64-devel] Mini-OS registers and libgcc
Index(es):
- Date
- Thread

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