Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@cthulhu.engr.sgi.com>
To: "Harald Koerfgen" <Harald.Koerfgen@home.ivm.de>
Cc: linux@cthulhu.engr.sgi.com, Florian Lohoff <flo@rfc822.org>,
	"Kevin D. Kissell" <kevink@mips.com>
Subject: Re: Decstation 5000/150 2.3.21 Boot successs
Date: Fri, 7 Jan 2000 17:30:04 -0800 (PST)	[thread overview]
Message-ID: <14454.37660.212667.920493@liveoak.engr.sgi.com> (raw)
In-Reply-To: <XFMail.000107200905.Harald.Koerfgen@home.ivm.de>

Harald Koerfgen writes:
 > 
 > On 06-Jan-00 William J. Earl wrote:
 > >      Note that the SVR4 MIPS ABI assumes FR=0 (R3000-compatible), as
 > > do SGI IRIX "-32" ("O32") binaries (and, I believe, default gcc
 > > binaries).  SGI IRIX "-n32" and "-n64" binaries assumes FR=1
 > > (R4000-compatible), and also have a somewhat different register calling
 > > convention (which affects where arguments to system calls reside).
 > 
 > Wouldn't it make sense then if we made FR=0 the default for Linux/MIPS?

      FR should be tied to the compilation model, which is reflected
in the magic number of the executable.  For "-32" ("O32"), FR must be 0.
That is, there is no need for default; exec should set FR appropriately.

  parent reply	other threads:[~2000-01-08  1:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06  9:12 Decstation 5000/150 2.3.21 Boot successs Kevin D. Kissell
2000-01-06  9:12 ` Kevin D. Kissell
2000-01-06 14:26 ` Ralf Baechle
2000-01-06 19:10   ` William J. Earl
2000-01-06 18:57 ` William J. Earl
2000-01-06 18:57   ` William J. Earl
2000-01-07 19:09   ` Harald Koerfgen
2000-01-07 23:29     ` Ralf Baechle
2000-01-08  1:30     ` William J. Earl [this message]
2000-01-08 23:12 ` Newer build tools John Michael Clemens
2000-01-10  4:01   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06 15:19 Decstation 5000/150 2.3.21 Boot successs Kevin D. Kissell
2000-01-06 15:19 ` Kevin D. Kissell
2000-01-06 23:54 ` Ralf Baechle
2000-01-07  1:50   ` William J. Earl
2000-01-05 21:18 Florian Lohoff

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=14454.37660.212667.920493@liveoak.engr.sgi.com \
    --to=wje@cthulhu.engr.sgi.com \
    --cc=Harald.Koerfgen@home.ivm.de \
    --cc=flo@rfc822.org \
    --cc=kevink@mips.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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