unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Jason Hemann <jason.hemann@gmail.com>
To: 56543@debbugs.gnu.org
Subject: bug#56543: bitwise-rotate-bit-field causes gmp overflow
Date: Wed, 13 Jul 2022 17:55:25 -0400	[thread overview]
Message-ID: <CALcHBdEcfLPMSiopsoxUL38UW9eRw2uK0CWJ2ExgyBK3Y_N2xQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

When I run Göran Weinholt's schjig <https://gitlab.com/weinholt/schjig>'s
`schjig.scm` against guile 3.0.8 I encounter the following error. Please
notice that I first switch on r6rs compatibility mode. I have no `.guile`
file. I did not see this listed on the R6RS incompatibilities
<https://www.gnu.org/software/guile/manual/html_node/R6RS-Incompatibilities.html>.
Is this a bug, either in guile or gmp?

```shell
$ guile
(install-r6rs!)
(load "schjig.scm")
...
(check (bitwise-rotate-bit-field 573972483446053417 1238 4006 -1627) =>
(quote 573972483446053417))
gmp: overflow in mpz type
Abort trap: 6
```

Best,

JBH

[-- Attachment #2: Type: text/html, Size: 3023 bytes --]

                 reply	other threads:[~2022-07-13 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALcHBdEcfLPMSiopsoxUL38UW9eRw2uK0CWJ2ExgyBK3Y_N2xQ@mail.gmail.com \
    --to=jason.hemann@gmail.com \
    --cc=56543@debbugs.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).