From: bonfacemunyoki@gmail.com (Bonface M. K.)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludovic.courtes@inria.fr>,
"simon tournier" <simon.tournier@univ-paris-diderot.fr>,
guix-hpc@gnu.org
Subject: Re: Reproducible Research Hackathon: Friday, July 3rd
Date: Tue, 14 Jul 2020 11:54:39 +0300 [thread overview]
Message-ID: <86tuyaeasw.fsf@gmail.com> (raw)
In-Reply-To: <m1wo36ms3c.fsf@fastmail.net> (Konrad Hinsen's message of "Tue, 14 Jul 2020 10:13:59 +0200")
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Hi Ludo,
>
>> Apologies for the delay. What was this bug exactly?
>>
>> I know Bonface addressed an issue related to how the Python 2.4 build
>> system would capture the kernel version via ‘uname’ a build time:
>>
>> https://gitlab.inria.fr/guix-hpc/guix-past/-/commit/d1977f5dccd73341f363cfa8d58ae3f2b2700ad7
>>
>> But presumably you’re referring to something else, right?
>
> Indeed. The details are here:
>
> https://gitlab.inria.fr/guix-hpc/guix-past/-/issues/1
>
> Since I won't be able to look into this before my summer vacations,
> I opened an issue as a reminder.
>
> Cheers,
> Konrad
>
That's strange. To get the right results, you'd have to do a `2L ** 64`.
When I tried `2 ** 63` I got `-9223372036854775808`. There's also an
overflow error. Here's a snippet of what fails from
Python-2.4.6/Lib/test:
```
# If this fails, probably using a strict IEEE-754 conforming libm, and x
# is +Inf afterwards. But Python wants overflows detected by default.
try:
x = math.exp(1000000000)
except OverflowError:
pass
else:
raise TestFailed("overflowing exp() didn't trigger OverflowError")
```
Maybe there's an overflow somewhere and we'd have to tweak libm? I'm
speculating though. I'd have to investigate this later.
--
Bonface M. K. (https://www.bonfacemunyoki.com)
One Divine Emacs To Rule Them All
GPG key = D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
next prev parent reply other threads:[~2020-07-14 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 12:40 Reproducible Research Hackathon: Friday, July 3rd simon tournier
2020-07-01 4:57 ` Pjotr Prins
2020-07-01 9:10 ` zimoun
2020-07-01 9:21 ` Efraim Flashner
2020-07-03 17:10 ` zimoun
2020-07-03 17:36 ` Ricardo Wurmus
2020-07-03 17:56 ` Paul Garlick
2020-07-03 18:19 ` zimoun
2020-07-07 17:52 ` Paul Garlick
2020-07-03 21:17 ` Ricardo Wurmus
2020-07-07 17:44 ` Paul Garlick
2020-07-04 9:51 ` Konrad Hinsen
2020-07-13 13:41 ` Ludovic Courtès
2020-07-14 8:13 ` Konrad Hinsen
2020-07-14 8:54 ` Bonface M. K. [this message]
2020-07-14 19:53 ` Konrad Hinsen
2020-07-14 13:18 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86tuyaeasw.fsf@gmail.com \
--to=bonfacemunyoki@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludovic.courtes@inria.fr \
--cc=simon.tournier@univ-paris-diderot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).