caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniil Baturin <daniil@baturin.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml 5.0, zeroth alpha release
Date: Wed, 15 Jun 2022 11:27:52 +0300	[thread overview]
Message-ID: <e6990cfb-c6fe-2999-83b4-c76b72788e6b@baturin.org> (raw)
In-Reply-To: <1886863657.25388002.1655281359972.JavaMail.zimbra@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 4314 bytes --]

Dear Florian,

This is exciting and I definitely will test all my projects with the alpha!

 >Notably, the native compiler will only be available on the ARM64 and
x86-64 architectures in this 5.0 release.

Is there a plan to re-introduce support for other architectures in later 
releases,
or will they dropped completely from the official scope?

On 6/15/22 11:22, Florian Angeletti wrote:
> Dear OCaml users,
>
> Five months after the initial merge of the multicore branch into the 
> mainline
> OCaml and three months after the release of OCaml 4.14.0, OCaml 5.0.0 is
> starting to take shape.
>
> I am thus happy to announce an exceptional zeroth alpha release of
> OCaml 5.0.0 (see below for the installation instructions).
>
> This alpha release is expected to be rougher than an usual alpha release,
> due to the full rewrite of the OCaml runtime. In particular, the bytecode
> debugger will only be available in the next alpha release. Similarly, 
> there
> will be some changes to the internal C runtime API and to the files 
> installed
> by the compiler package in the next alpha release.
>
> Moreover, this zeroth alpha release is the occasion to remind everyone 
> that
> OCaml 5.0 itself is expected to be a more experimental release than usual.
> Notably, the native compiler will only be available on the ARM64 and
> x86-64 architectures in this 5.0 release.
>
> Nevertheless, this zeroth alpha version is already stable enough for 
> fellow
> hackers eager to join us in our early bug hunting and opam ecosystem 
> fixing fun,
> or to venture in the new era of parallelism and (experimental) effects.
>
> You can follow the progresses in stabilising the opam ecosystem on
>
> https://github.com/ocaml/opam-repository/issues/21526
>
> A brief summary is that at least dune, merlin, ppxlib, utop, ocamlfind,
> and ocamlbuild work (potentially by using patches from the
> alpha opam repository).
>
> If you find any bugs, please report them here:
>
> https://github.com/ocaml/ocaml/issues
>
> In particular, any sequential OCaml 4 library or program should be 
> valid in
> OCaml 5 (except for deprecated modules and functions). Please don't 
> hesitate
> to report any forward-compatibility bugs!
>
> If you are interested by the ongoing list of bug fixes, the
> updated change log for OCaml 5.0.0 is available at:
>
> https://github.com/ocaml/ocaml/blob/5.0/Changes
>
> Happy hacking,
> Florian Angeletti for the OCaml team.
>
> Installation instructions
> -------------------------
> The base compiler can be installed as an opam switch with the 
> following commands
> on opam 2.1:
>
> opam update
> opam switch create 5.0.0~alpha0
>
> For previous version of opam, the switch creation command line is 
> slightly more verbose:
>
> opam update
> opam switch create 5.0.0~alpha0 
> --repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
>
> If you want to tweak the configuration of the compiler, you can switch 
> to the option variant with:
>
> opam update
> opam switch create <switch_name> ocaml-variants.5.0.0~alpha0+options 
> <option_list>
>
> where <option_list> is a comma separated list of ocaml-option-* 
> packages. For instance, for a flambda and no-flat-float-array switch:
>
> opam switch create 5.0.0~alpha0+flambda+nffa 
> ocaml-variants.5.0.0~alpha0+options ocaml-option-flambda 
> ocaml-option-no-flat-float-array
>
> The command line above is slightly more complicated for an opam 
> version anterior to opam 2.1:
>
> opam update
> opam switch create <switch_name> 
> --packages=ocaml-variants.5.0.0~alpha0+options,<option_list> 
> --repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
>
> In both cases, all available options can be listed with
> "opam search ocaml-option".
>
> If you want to test this version, it is strongly advised to install 
> the alpha
> opam repository
>
> https://github.com/kit-ty-kate/opam-alpha-repository
>
> with
>
> opam repo add alpha git://github.com/kit-ty-kate/opam-alpha-repository.git
>
> This alpha repository contains various fixes in the process of being 
> upstreamed.
>
> The source code for the alpha is also available at these addresses:
>
> https://github.com/ocaml/ocaml/archive/5.0.0-alpha0.tar.gz
> https://caml.inria.fr/pub/distrib/ocaml-5.0/ocaml-5.0.0~alpha0.tar.gz
>

[-- Attachment #2: Type: text/html, Size: 6984 bytes --]

  reply	other threads:[~2022-06-15  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  8:22 Florian Angeletti
2022-06-15  8:27 ` Daniil Baturin [this message]
2022-06-15  9:36   ` Florian Angeletti
2022-07-22  8:33 ` [Caml-list] OCaml 5.0, first normal " Florian Angeletti

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=e6990cfb-c6fe-2999-83b4-c76b72788e6b@baturin.org \
    --to=daniil@baturin.org \
    --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;
as well as URLs for NNTP newsgroup(s).