[Mono-list] Endian issue
Neale.Ferguson@SoftwareAG-USA.com
Neale.Ferguson@SoftwareAG-USA.com
Fri, 21 May 2004 14:48:31 -0400
This is a multi-part message in MIME format.
------_=_NextPart_001_01C43F64.36ACA6D3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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=20
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_001_01C43F64.36ACA6D3
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Endian issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>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:<BR>
<BR>
0000000 4d5a 0000 =
0600 0000 0400<BR>
<BR>
instead of<BR>
<BR>
0000000 5a4d 0000 =
0006 0000 0004<BR>
<BR>
S390 is big endian. I see there is a BitConverter class that works it =
out but does mcs use this or some other method?<BR>
<BR>
Neale</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C43F64.36ACA6D3--