Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Ken Wakita <Ken.Wakita@is.titech.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: Ocamlopt for R4000?
Date: Thu, 16 Sep 1999 15:22:24 +0200	[thread overview]
Message-ID: <19990916152224.28684@pauillac.inria.fr> (raw)
In-Reply-To: <37D79CA3280.39A6KEN.WAKITA@mail.is.titech.ac.jp>; from Ken Wakita on Thu, Sep 09, 1999 at 08:40:19PM +0900

> Thank you very much for your information.
> 
> We already met the signal handling problem and tried to fix it.  The
> thing even worse is that the assembler that comes with Cenju-4 does not
> accept 64bit code.  It might be the case that the MPU version is
> R3000???

Probably not, but all MIPS processors can be run in R3000
compatibility mode, where the 64-bit instructions are not accessible
and there are only 16 64-bit floating-point registers.  (This is what
SGI calls the "o32" model under IRIX.)  It seems like your machine is
doing this.

The ocamlopt compiler used to produce "o32" code, but then SGI IRIX
phased out "o32", forcing us to switch to the new "n32" code model.

You have basically two options at this point:

- See whether the assembler/linker/C compiler on your machine can be
  configured for a code model similar to IRIX's "n32".  (On IRIX,
  cc, as and ld have command-line options and environment variables
  that let the programmer choose the code model.)

- Downgrade OCaml to version 2.01, which still contains support for
  the "o32" code model.

Regards,

- Xavier Leroy




      parent reply	other threads:[~1999-09-17 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-23  8:43 Ken Wakita
1999-08-23 15:55 ` Yozo Toda
1999-08-31 19:16 ` Xavier Leroy
1999-09-01 15:23   ` Y2K related changes Friedman Roy
1999-09-06 17:52     ` Xavier Leroy
     [not found]   ` <37D79CA3280.39A6KEN.WAKITA@mail.is.titech.ac.jp>
1999-09-16 13:22     ` Xavier Leroy [this message]

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=19990916152224.28684@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=Ken.Wakita@is.titech.ac.jp \
    --cc=caml-list@inria.fr \
    /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