From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] OCaml 4.13.0, second release candidate
Date: Thu, 16 Sep 2021 10:32:28 +0200 (CEST) [thread overview]
Message-ID: <312776328.23426167.1631781148096.JavaMail.zimbra@inria.fr> (raw)
In-Reply-To: <623764070.13369101.1631279120562.JavaMail.zimbra@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]
Dear OCaml users,
The release of OCaml 4.13.0 is expected for next week.
Since we had a native code generation bug fix and two minor configuration tweaks
since the first release candidate, we are publishing a second release candidate.
If you find any bugs, please report them here:
https://github.com/ocaml/ocaml/issues
Happy hacking,
Florian Angeletti for the OCaml team.
Installation instructions
----------------------------
The base compiler can be installed as an opam switch with the following commands
opam update
opam switch create 4.13.0~rc2 --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> --packages=ocaml-variants.4.13.0~rc2+options,<option_list> --repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
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 4.13.0~rc2+flambda+nffa --packages=ocaml-variants.4.13.0~rc2+options,ocaml-option-flambda,ocaml-option-no-flat-float-array --repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
All available options can be listed with "opam search ocaml-option".
The source code for the release candidate is also available at these addresses:
https://github.com/ocaml/ocaml/archive/4.13.0-rc2.tar.gz
https://caml.inria.fr/pub/distrib/ocaml-4.13/ocaml-4.13.0~rc2.tar.gz
Changes since the first release candidate
------------------------------------------------------
- #10626, #10628: Wrong reloading of the x86-64 instruction for
integer multiplication by a constant, causing the assembler to
reject the ocamlopt-generated code.
(Xavier Leroy, report by Dave Aitken, review by Vincent Laviron)
+ #10176, #10632(new in rc2): By default, call the assembler through the C compiler driver
(Sébastien Hinderer, review by Gabriel Scherer, David Allsopp and Xavier
Leroy)
+ #10451, #10635(new in rc2): Replace the use of iconv with a C utility to convert $(LIBDIR)
to a C string constant on Windows when building the runtime. Hardens the
generation of the constant on Unix for paths with backslashes, double-quotes
and newlines.
(David Allsopp, review by Florian Angeletti and Sébastien Hinderer)
[-- Attachment #2: Type: text/html, Size: 2778 bytes --]
prev parent reply other threads:[~2021-09-16 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 18:34 [Caml-list] OCaml 4.13.0, first alpha release Florian Angeletti
2021-07-19 8:08 ` [Caml-list] OCaml 4.13.0, second " Florian Angeletti
2021-08-25 18:16 ` [Caml-list] OCaml 4.13.0, first beta release Florian Angeletti
2021-09-10 13:05 ` [Caml-list] OCaml 4.13.0, first release candidate Florian Angeletti
2021-09-16 8:32 ` Florian Angeletti [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=312776328.23426167.1631781148096.JavaMail.zimbra@inria.fr \
--to=florian.angeletti@inria.fr \
--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