From: Maxime Devos <maximedevos@telenet.be>
To: Thomas Thiriez <thomas@twistedwave.com>, guile-user@gnu.org
Subject: Re: 64-bit Guile on Windows
Date: Tue, 28 Jun 2022 18:14:22 +0200 [thread overview]
Message-ID: <a3defa1e0ce52e5cad5bb675a1c99f7ada9e205d.camel@telenet.be> (raw)
In-Reply-To: <m2pmisu9kz.fsf@twistedwave.com>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
Thomas Thiriez via General Guile related discussions schreef op di 28-
06-2022 om 16:41 [+0200]:
> Jean Abou Samra <jean@abou-samra.fr> writes:
>
> > Le 27/06/2022 à 15:56, Thomas Thiriez via General Guile related
> > discussions a écrit :
> [...]
> > > (* 999 999 999) -> -76738825
> [...]
> >
> > We had exactly the same problem at LilyPond, and this was the
> > fix:
> >
> > https://gitlab.com/lilypond/lilypond/-/blob/master/release/binaries/lib/dependencies.py#L721
> >
> > Namely, you need to patch libguile/conv-integer.i.c and
> > conv-uinteger.i.c to replace "SIZEOF_TYPE < SIZEOF_SCM_T_BITS"
> > with "SIZEOF_TYPE < SIZEOF_LONG".
> >
> > HTH,
> > Jean
>
> Thanks for the info. I have tried this, but it doesn't appear to
> be helping.
>
> I did a few tests with lilypond, and here is what I found. I have
> a test.scm file containing:
>
> (display (* 999)) (newline)
> (display (* 999 999)) (newline)
> (display (* 999 999 999)) (newline)
>
> lilypond.exe -e '(load \"test.scm\")' test.ly
> GNU LilyPond 2.23.10 (running Guile 2.2)
> 999
> 998001
> 997002999
>
> That is fine. Now, if I try compiling test.scm to test.go, I get:
>
> lilypond.exe -e '(use-modules (system base compile))(compile-file
> \"test.scm\" #:output-file \"test.go\")' test.ly
> GNU LilyPond 2.23.10 (running Guile 2.2)
> ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
> In procedure bytevector-u64-set!: Value out of range: -149659645
You can find some possibly related bugs on debbugs:
Possibly fixnum-related, so maybe:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42060
Maybe 32-bit <-> 64-bit related, so maybe:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28920
Also, guile@2.2 is not developed anymore AFAICT.
Greetings,
Maixme.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-28 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:56 64-bit Guile on Windows Thomas Thiriez via General Guile related discussions
2022-06-27 17:28 ` Jan Nieuwenhuizen
2022-06-27 19:33 ` Thomas Thiriez via General Guile related discussions
2022-06-28 8:38 ` Jean Abou Samra
2022-06-28 10:52 ` Maxime Devos
2022-07-06 16:33 ` Jean Abou Samra
2022-06-28 14:41 ` Thomas Thiriez via General Guile related discussions
2022-06-28 15:00 ` Thomas Thiriez via General Guile related discussions
2022-06-28 16:14 ` Maxime Devos [this message]
2022-06-28 22:07 ` Dr. Arne Babenhauserheide
2022-06-29 9:07 ` Thomas Thiriez via General Guile related discussions
2022-11-22 12:44 ` Jean Abou Samra
2022-11-22 13:22 ` Mike Gran
2023-03-23 23:14 ` Thomas Thiriez via General Guile related discussions
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 14:32 Jean Abou Samra
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=a3defa1e0ce52e5cad5bb675a1c99f7ada9e205d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-user@gnu.org \
--cc=thomas@twistedwave.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.
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).