[Mono-list] Endian issue
Daniel Morgan
danielmorgan@verizon.net
Tue, 25 May 2004 20:56:59 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_0001_01C4429A.D3076310
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hello Neale,
I don't know if my earlier email reached you, so I will ask here.
Do you have access to a s390, or do you use Hercules emulator?
I'm curious, what does one need to get mono up and running on s390?
Daniel
-----Original Message-----
From: mono-list-admin@lists.ximian.com
[mailto:mono-list-admin@lists.ximian.com] On Behalf Of
Neale.Ferguson@SoftwareAG-USA.com
Sent: Friday, May 21, 2004 2:49 PM
To: mono-list@ximian.com
Subject: [Mono-list] Endian issue
My S390 JIT is almost doing the right thing. Apart from some exception
handling issues things look pretty good. However, when I run the
compiler with the JIT the byte ordering is a problem. For example I
produce:
0000000 4d5a 0000 0600 0000 0400
instead of
0000000 5a4d 0000 0006 0000 0004
S390 is big endian. I see there is a BitConverter class that works it
out but does mcs use this or some other method?
Neale
------=_NextPart_000_0001_01C4429A.D3076310
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2>Hello=20
Neale,</FONT></SPAN></DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
don't know if my earlier email reached you, so I will ask=20
here.</FONT></SPAN></DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2>Do you=20
have access to a s390, or do you use Hercules =
emulator?</FONT></SPAN></DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2>I'm=20
curious, what does one need to get mono up and running on=20
s390?</FONT></SPAN></DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2>Daniel</FONT></SPAN></DIV>
<DIV><SPAN class=3D750175500-26052004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV></DIV>
<DIV><FONT face=3DTahoma size=3D2>-----Original =
Message-----<BR><B>From:</B>=20
mono-list-admin@lists.ximian.com =
[mailto:mono-list-admin@lists.ximian.com] <B>On=20
Behalf Of </B>Neale.Ferguson@SoftwareAG-USA.com<BR><B>Sent:</B> Friday, =
May 21,=20
2004 2:49 PM<BR><B>To:</B> mono-list@ximian.com<BR><B>Subject:</B> =
[Mono-list]=20
Endian issue<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><!-- Converted from =
text/plain format -->
<P><FONT size=3D2>My S390 JIT is almost doing the right thing. Apart =
from some=20
exception handling issues things look pretty good. However, when I run =
the=20
compiler with the JIT the byte ordering is a problem. For example I=20
produce:<BR><BR>0000000 4d5a =20
0000 0600 0000 =20
0400<BR><BR>instead of<BR><BR>0000000 =
5a4d =20
0000 0006 0000 =20
0004<BR><BR>S390 is big endian. I see there is a BitConverter class =
that works=20
it out but does mcs use this or some other method?<BR><BR>Neale</FONT> =
</P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0001_01C4429A.D3076310--