all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Bengt Richter <bokr@bokr.com>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Feedback from JRES in Dijon
Date: Fri, 06 Dec 2019 13:24:57 +0100	[thread overview]
Message-ID: <m1immty73a.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <20191206070455.GA28637@PhantoNv4ArchGx.localdomain>

Hi Bengt,

>> [1] https://webcast.in2p3.fr/video/les-enjeux-et-defis-de-la-recherche-reproductible
>> https://aramis.resinfo.org/wiki/lib/exe/fetch.php?media=pleniaires:aramis_keynote_enjeux-et-defis-recherche-reproductible_konrad_hinsen.pdf
>>
>
> Is [1] available as a libre video download?

No idea. I can answer most questions about the content since I am the
speaker, but I was not involved with recording and publishing.

> IMO if you can't reproduce bit-identical results, you should find out _exactly_ why.
> And if you do get exactly the same result, you should also know exactly why ;-)

That's a nice way to put it!

> The video touches on IEEE 754 (and I do believe the lecturer
> understands these issues, but he says (IIU.fr :) no programming
> language gives control over the FPU -- is that true?? I mean,
> including on-the-metal x86_64 assembly language??

I wouldn't count that as a programming language, but that is of course
debatable. For me, a programming language is a platform-neutral medium
that can be run on any type of computer. And yes, you can argue that
the subset of x86 assembly that doesn't manipulate hardware other than
registers fits that definition, but you have to draw the line somewhere.

More interestingly (definitions aren't really interesting), I am of
course not certain that there is no programming language that gives
access to the full IEEE754 programming model. I am not aware of any,
but if there is, I'd like to find out!

> BTW, if you are interested in floating point, links from here should be fun:
>
> --8<---------------cut here---------------start------------->8---
> https://en.wikipedia.org/wiki/William_Kahan
> --8<---------------cut here---------------end--------------->8---

Indeed. For those unfamiliar with that name, Kahan designed the 8087
floating-point processor for Intel and was the main driver behind the
IEEE 754 standardization effort.

Cheers,
  Konrad.

  reply	other threads:[~2019-12-06 14:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42   ` Julien Lepiller
2019-12-05 15:44     ` Konrad Hinsen
2019-12-05 15:52       ` zimoun
2019-12-06  7:07         ` Bengt Richter
2019-12-06 12:24           ` Konrad Hinsen [this message]
2019-12-07 16:35             ` Timothy Sample
2019-12-08  2:48               ` Bengt Richter
2019-12-08  4:11                 ` Timothy Sample
2019-12-08 23:09                   ` Bengt Richter
2019-12-09  5:23                     ` Konrad Hinsen
2019-12-06 12:57         ` Konrad Hinsen
2019-12-10 16:57           ` Ludovic Courtès
2019-12-11 20:48             ` Konrad Hinsen
2020-01-07 16:05           ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40             ` zimoun
2020-01-10 16:59             ` Ludovic Courtès
2020-01-10 17:19               ` zimoun
2020-01-10 18:53               ` Giovanni Biscuolo
2020-01-11  9:31               ` Konrad Hinsen
2020-01-11 14:05                 ` Giovanni Biscuolo
2020-01-13  8:37                 ` Ludovic Courtès
2020-01-14  9:06               ` Konrad Hinsen
2020-01-14 15:38                 ` Ludovic Courtès
2020-01-14 16:18                   ` Konrad Hinsen
2020-01-14 16:40                     ` Ludovic Courtès
2020-01-10 17:03             ` Ludovic Courtès
2020-01-11  9:39               ` Konrad Hinsen
2020-01-15 22:20                 ` Ludovic Courtès
2019-12-05 15:47     ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` Ludovic Courtès

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=m1immty73a.fsf@ordinateur-de-catherine--konrad.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.