unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Thiriez via General Guile related discussions <guile-user@gnu.org>
To: guile-user@gnu.org
Subject: Re: 64-bit Guile on Windows
Date: Tue, 28 Jun 2022 16:41:44 +0200	[thread overview]
Message-ID: <m2pmisu9kz.fsf@twistedwave.com> (raw)
In-Reply-To: <adb9c207-777f-5b74-c026-aaa3661cb582@abou-samra.fr>


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

That doesn't work, so I compile test.scm to test.go with guile on 
my Mac. If I then try loading the generated test.go with lilypond, 
I get:

lilypond.exe -e '(load \"test.go\")' test.ly
GNU LilyPond 2.23.10 (running Guile 2.2)
999
998001
-76738825

Now, it is possible that the problem is that I am trying to run a 
.go file compiled on macOS on a Windows machine, and that the two 
platforms are different enough that the .go file can't be reused. 
And because I get that "Value out of range" error when compiling 
on Windows, I am probably stuck with .scm files instead of 
compiled .go files.

Regards,
Thomas Thiriez



  parent reply	other threads:[~2022-06-28 14:41 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 [this message]
2022-06-28 15:00     ` Thomas Thiriez via General Guile related discussions
2022-06-28 16:14     ` Maxime Devos
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=m2pmisu9kz.fsf@twistedwave.com \
    --to=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).