GNU bug report logs - #48150
breaking gmp

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: lloda <lloda <at> sarc.name>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#48150: closed (breaking gmp)
Date: Fri, 05 Nov 2021 16:34:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 5 Nov 2021 17:33:16 +0100
with message-id <9186B091-39D6-4855-838E-ABC4952DAEC1 <at> sarc.name>
and subject line Re: breaking gmp
has caused the debbugs.gnu.org bug report #48150,
regarding breaking gmp
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
48150: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48150
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Zefram <zefram <at> fysh.org>
To: bug-guile <at> gnu.org
Subject: breaking gmp
Date: Sun, 2 May 2021 02:14:46 +0100

With Guile 2.2.6:

$ guile-2.2 -c '(ash 1 (ash 1 37))'
gmp: overflow in mpz type
zsh: abort      guile-2.2 -c '(ash 1 (ash 1 37))'
$

For shift distances of (ash 1 63) or greater Guile cleanly signals an
exception indicating the overflow.  The above treatment of a range of
smaller (but still stupidly large) shift distances is less than awesome.
It would be preferable for Guile to know gmp's limits and cleanly signal
an exception, rather than exceed those limits in a way that terminates
the process outright.

-zefram

[Message part 3 (message/rfc822, inline)]

From: lloda <lloda <at> sarc.name>
To: 48150-done <at> debbugs.gnu.org
Subject: Re: breaking gmp
Date: Fri, 5 Nov 2021 17:33:16 +0100

Fixed in bf9d30f3c3fd03cb37d604f1927e9ce5c699338b. Thanks!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.