From: e@x80.org (Emilio Jesús Gallego Arias)
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Xavier Leroy <xavier.leroy@inria.fr>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [IMPORTANT] Intel Skylake / Kaby Lake hardware bug affects OCaml programs
Date: Fri, 30 Jun 2017 17:31:44 +0200 [thread overview]
Message-ID: <84injdfq5b.fsf@kaguya> (raw)
In-Reply-To: <CAPFanBEwTMtfoKcBy9bNgdjC7u81wGn+ehBLiwaU7fRtg_oi8A@mail.gmail.com> (Gabriel Scherer's message of "Fri, 30 Jun 2017 11:17:26 -0400")
Gabriel Scherer <gabriel.scherer@gmail.com> writes:
> Here is my list of affected OCaml projects known so far (it seems
> surprisingly less rare than I thought at first):
>
> - an (unnamed) industrial user noticed the issue in Spring 2016, as
> reported by Xavier on the bugtracker:
> https://caml.inria.fr/mantis/view.php?id=7452#c17109
>
> - ahrefs noticed issues in late 2016, as reported by Joris
> Giovannangeli on the bugtracker issue or his longer piece
> https://tech.ahrefs.com/skylake-bug-a-detective-story-ab1ad2beddcd
>
> - Lwt users were also affected (first report from Sebastien Mondet in
> February 2017):
> https://github.com/ocsigen/lwt/issues/315
>
> - Julia Lawall reported segfaults from a downstream user on the caml-list,
> that seem extreley likely to be related to this issue (they
> disappear with hyperthreading disabled)
> https://sympa.inria.fr/sympa/arc/caml-list/2017-06/msg00115.html
Here is the only Coq bug that I know of:
https://coq.inria.fr/bugs/show_bug.cgi?id=5517
but as Maxime pointed out, the problem was observed by other people
internally.
E.
next prev parent reply other threads:[~2017-06-30 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:51 Xavier Leroy
2017-06-30 14:15 ` Xavier Leroy
2017-06-30 15:17 ` Gabriel Scherer
2017-06-30 15:31 ` Emilio Jesús Gallego Arias [this message]
2017-06-30 16:30 ` Julia Lawall
2017-06-30 16:46 ` Anton Bachin
2017-06-30 17:03 ` Xavier Leroy
2017-07-05 1:01 ` Johannes Kanig
2017-06-30 15:28 ` Mark Shinwell
2017-06-30 15:19 ` Maxime Dénès
2017-06-30 15:38 ` Anton Bachin
2017-07-21 13:00 ` David MENTRÉ
2017-07-22 7:27 ` Gabriel Scherer
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=84injdfq5b.fsf@kaguya \
--to=e@x80.org \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=xavier.leroy@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