From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <c4893c796bd98bd3f90a12b821cd70d8@coraid.com>
References: <1ebc06ba0079a91546444a93ab21bc65@quintile.net>
	<12706eb9d1aafea3af76c427a31aae1a@coraid.com>
	<CAJSxfmK4DhVFsCa97+RSeR2biFRSw7rQ9bvk=N4cK56wdwTVww@mail.gmail.com>
	<c4893c796bd98bd3f90a12b821cd70d8@coraid.com>
Date: Wed, 27 Nov 2013 11:24:37 -0800
Message-ID: <CAJSxfm+xBnY1QdgsEH_yTXt1sxVHqn+_zXumOrpn=s-raJ+XkQ@mail.gmail.com>
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: erik quanstrom <quanstro@labs.coraid.com>
Content-Type: multipart/alternative; boundary=089e013d0dc048511604ec2d8cba
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] compiler bug?
Topicbox-Message-UUID: 8c541402-ead8-11e9-9d60-3106f5b1d025

--089e013d0dc048511604ec2d8cba
Content-Type: text/plain; charset=ISO-8859-1

the Go to C switch got me :) (no breaks!); couldn't see why more than one
byte was getting the 'x' value! changing buf to "1234" made it more obvious.


On Wed, Nov 27, 2013 at 10:38 AM, erik quanstrom
<quanstro@labs.coraid.com>wrote:

> On Wed Nov 27 13:07:31 EST 2013, skip.tavakkolian@gmail.com wrote:
>
> > why is mips different (erik's version)?
> >
> > supermic% ./8.out
> > 78780000
> > mikro% ./v.out
> > 7878
> > rpi% ./5.out
> > 78780000
> >
>
> because it's big endian.  what you're doing there is
> putting bytes in specific positions.  in this case you have
> bytes (in hex):
>
>         0 0 78 78
>
> on a little endian machine this is 0x78780000 and on a
> big-endian machine this is 0x00007878.
>
> - erik
>

--089e013d0dc048511604ec2d8cba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">the Go to C switch got me :) (no breaks!); couldn&#39;t se=
e why more than one byte was getting the &#39;x&#39; value! changing buf to=
 &quot;1234&quot; made it more obvious.</div><div class=3D"gmail_extra"><br=
>
<br><div class=3D"gmail_quote">On Wed, Nov 27, 2013 at 10:38 AM, erik quans=
trom <span dir=3D"ltr">&lt;<a href=3D"mailto:quanstro@labs.coraid.com" targ=
et=3D"_blank">quanstro@labs.coraid.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<div class=3D"im">On Wed Nov 27 13:07:31 EST 2013, <a href=3D"mailto:skip.t=
avakkolian@gmail.com">skip.tavakkolian@gmail.com</a> wrote:<br>
<br>
&gt; why is mips different (erik&#39;s version)?<br>
&gt;<br>
&gt; supermic% ./8.out<br>
&gt; 78780000<br>
&gt; mikro% ./v.out<br>
&gt; 7878<br>
&gt; rpi% ./5.out<br>
&gt; 78780000<br>
&gt;<br>
<br>
</div>because it&#39;s big endian. =A0what you&#39;re doing there is<br>
putting bytes in specific positions. =A0in this case you have<br>
bytes (in hex):<br>
<br>
=A0 =A0 =A0 =A0 0 0 78 78<br>
<br>
on a little endian machine this is 0x78780000 and on a<br>
big-endian machine this is 0x00007878.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
- erik<br>
</font></span></blockquote></div><br></div>

--089e013d0dc048511604ec2d8cba--