From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] MIPS LE fp register ordering in MOVD
Date: Fri, 27 Dec 2013 06:41:44 +0200 [thread overview]
Message-ID: <5905828a43a7658265a86f484a46aba6@proxima.alt.za> (raw)
In-Reply-To: <CAJQxxwkLNAQ2M3aTFD3OZQ=X14TMABXGs0ow=i_79S9XYr_ohA@mail.gmail.com>
> You might be able to blame the play station 2 and the two different MIPS
> chips it had. I did two compilers. The FP was very unusual and one was LE
> and the other BE. Inferno port worked well.
Eventually, it seems that the second compiler was somehow absorbed: 0c
became a script to invoke vc, or somesuch. Could you shed some light
on this? Or was forsyth involved? Bell Labs are consistently short
on rationales.
++L
next prev parent reply other threads:[~2013-12-27 4:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 17:20 cherry
2013-12-26 23:46 ` cherry
2013-12-26 23:48 ` erik quanstrom
2013-12-27 0:25 ` cherry
2013-12-27 1:40 ` cinap_lenrek
2013-12-27 3:40 ` cherry
2013-12-30 7:12 ` Skip Tavakkolian
2013-12-27 3:41 ` cherry
2013-12-27 4:32 ` Bruce Ellis
2013-12-27 4:41 ` lucio [this message]
2013-12-27 22:32 ` Bruce Ellis
2013-12-28 1:22 ` cherry
2013-12-28 1:47 ` Bruce Ellis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5905828a43a7658265a86f484a46aba6@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).