So that all AMD64 cases come before the ARM and ARM64 cases.

Using the "return after stack overflow" approach.

Fixes:  ocaml#10547

Stack overflow detection and naked pointers checking for ARM64 (Linux and macOS)

These functions have been marked as deprecated for a while, are superseded by functions from the Marshal module, and seem unused in OPAM packages.  Plus, this removes the dependency of Obj on Marshal.

The presence of this field will be checked by opam lint starting with opam 2.2.0

Typos

Fixes ocaml#9116

When we run

    List.init 300 (Fun.const "a")

we can see that the toplevel in one case prints

    ""... (* string length 1; truncated *)

instead of just "a". The comment that the string was truncated takes at
least 36 characters, so truncating does not make much sense here.
If we are going to print the comment, it doesn't hurt much to also show
a part of the string to the user.

A byte can be printed as up to 4 characters, due to escaping.
So printing strings of length up to 8 bytes will always be shorter
without truncating.

There are still cases when truncating gives a longer text than not,
but it's unavoidable if the length of the printed prefix is a
nondecreasing function of the string length.

oprint: Truncate strings only after 8 bytes

s390x: use 8 integer registers for parameter passing instead of 5.
POWER: use 16 integer registers for parameter passing instead of 8.
This makes tail calls more usable on these two platforms.
It brings them inline with ARM (8 param regs) and ARM64 and RISC-V (16 param regs).

The build system is vast enough without two names for the same thing!

Fix manpages build when libraries are disabled

Co-Authored-By: Pierre Chambart

(suggestion from Konstantin Romanov)

  Error when parsing the following phrase:
  let[@tail_mod_cons rec bind (f : 'a -> 'a tree) (t : 'a tree) : 'a tree =
  match t with
  | Leaf v -> (f[@tailcall false]) v
  | Node (left, right) -> Node (bind f left, (bind[@tailcall]) f right)

I'm not sure why I need to repeat the type definition from the
previous phrase, but I guess I need to go re-read the documentation of
caml_example to understand how state is preserved.

Nothing particularly worrying here.

  Uncaught exception: Failure("lexing: empty token")
  Fatal error: exception Failure("lexing: empty token")

  Error when evaluating a caml_example environment in extensions/tail_mod_cons.etex, line 176:
  Textual transforms must be well-separated.
  The "underline" transform spanned the interval 113-157,
  intersecting with another "underline" transform  on the 124-138 interval.
  Hind: did you try to elide a code fragment which raised a warning?

    Unknown caml_example option: [ok].
    Supported options are "ok","error", or "warning=n" (with n a warning number).

    Error when evaluating a caml_example environment in extensions/tail_mod_cons.etex, line 176:
    Textual transforms must be well-separated.
    The "underline" transform spanned the interval 113-157,
    intersecting with another "underline" transform  on the 124-138 interval.
    Hind: did you try to elide a code fragment which raised a warning?