gambit/gambit

Gambit is an efficient implementation of the Scheme programming language.

Bradley Lucier

@gambiteer

If you use it with gsc then that means that you're restricting the heap size of gsc when it runs. Perhaps you want to do

[Bradleys-Mac-mini:~] lucier% gsc -exe c.scm
[Bradleys-Mac-mini:~] lucier% ./c -:max-heap=1000
*** ERROR IN ##make-vector -- Heap overflow

junkerjoe

@junkerjoe

i think that's just what i needed

thank you!

from gsc -:help i would've thought the option would need to be provided with the compilation command

anyways that's great, and really simple too

Riley Levy

@rileylevy95_gitlab

To build a gambit program with emscripten, how do I get an emscripten version of libgambit.a?

Marc Feeley

@feeley

@junkerjoe you can also use the following trick... if your source program contains a shebang line gsc will read the runtime options on the shebang line and embed them in the executable. This is convenient if you program starts off as an interpreted script that is compiled when ready for production. For example :

% cat limited.scm
#! /usr/bin/env gsi -:max-heap=100M
(##gc-report-set! #t)
(##gc)
(define (go)
  (let loop ((size 1000000) (last #f))
    (println size)
    (loop (* size 2) (make-vector size))))
(with-exception-catcher pp go)
% chmod +x limited.scm
% ./limited.scm
*** GC: 135us, 130K alloc, 12M heap, 84K live (1% 84288+1488)
1000000
2000000
*** GC: 2.4ms, 135K alloc, 52M heap, 23M live (44% 85168+24001584)
4000000
*** GC: 5.1ms, 139K alloc, 101M heap, 46M live (46% 85168+48001584)
8000000
*** GC: 9.3ms, 143K alloc, 105M heap, 92M live (88% 85168+96001584)
16000000
*** GC: 17ms, 147K alloc, 108M heap, 61M live (57% 85168+64001536)
#<heap-overflow-exception #2>
% gsc -exe limited.scm
% ./limited
*** GC: 109us, 71K alloc, 12M heap, 64K live (1% 64464+1488)
1000000
2000000
*** GC: 525us, 75K alloc, 36M heap, 15M live (42% 64928+16001536)
4000000
*** GC: 260us, 79K alloc, 69M heap, 31M live (45% 64928+32001536)
8000000
*** GC: 1.9ms, 82K alloc, 108M heap, 61M live (57% 64928+64001536)
16000000
*** GC: 3.4ms, 86K alloc, 12M heap, 65K live (1% 64928+1488)
#<heap-overflow-exception #2>

@rileylevy95_gitlab Please check the file misc/build-gambit-emscripten.tgz... it is quite likely that it has suffered from bitrot, but it shouldn't be too hard to get it working again. This biggest problem is probably the evolution of emscripten, so doing a checkout of an old version of emscripten may be needed if you just want to quickly experiment with this.

Riley Levy

@rileylevy95_gitlab

Thank you

Ideally, would i run that script instead of ./configure?

junkerjoe

@junkerjoe

That is really useful. Thanks @feeley

luca regini

@lucaregini

Hi @feeley , how do you debug the gambit compiler? Do you run it completely in the interpreter? Do you start with the binary and then load in the interpreter what you'd like to debug?

luca regini

@lucaregini

By "debugging" I really intended single-stepping in the source of the compiler. What's the most convenient way to do that?

Bradley Lucier

@gambiteer

Try gsc/igsc.scm.

9 replies

François-René Rideau

@fare

In a clean git checkout of master, if I try to git checkout v4.9.3, I get an error about "local changes" to some files. My workaround was to use git worktree add v4.9.3 v4.9.3.

is it OK if the makefile tries to build some modules that fail with errors on some targets?

François-René Rideau

@fare

looks like gambit has been trying to compile _digest for riscv-64 at 100% cpu for 40 minutes.

Jaime Fournier

@ober

local changes happens I found when you are using a modified tree. git clean -xfd always fixed it for me. as per @belmarca advice

luca regini

@lucaregini

How to specify additional include directories in gsi?

luca regini

@lucaregini

(load "/home/lucar/gambit/gsc/igsc.scm")

ERROR -- Can't open file "/home/lucar/gambit-stage/usr/local/Gambit/lib/header.scm"
1>

Drew Crampsie

@drewc

@lucaregini http://www.iro.umontreal.ca/~gambit/doc/gambit.html#Runtime-options

luca regini

@lucaregini

@drewc I saw that section, which is the right option? I see only The ‘=DIRECTORY’ option overrides the setting of the central installation directory.
and
The ‘~~DIR=DIRECTORY’ option overrides the setting of the DIR installation directory.

These options are not what I am looking for

I need to add paths, not to ovveride the installation directory

Drew Crampsie

@drewc

If you (or the code) is using "~~" as a prefix to the libs, is that not by its very nature an installed gambit library?

(eval '(begin
        (##namespace ("c#"))
        (##include "~~/lib/header.scm")))

Bradley Lucier

@gambiteer

This seems to work

heine:~/programs/gambit/gambit> gsi -:=. gsc/igsc.scm 
loading "~~/gsc/_host.scm"
loading "~~/gsc/_utils.scm"
loading "~~/gsc/_source.scm"
loading "~~/gsc/_parms.scm"
loading "~~/gsc/_env.scm"
loading "~~/gsc/_ptree1.scm"
loading "~~/gsc/_ptree2.scm"
loading "~~/gsc/_gvm.scm"
loading "~~/gsc/_back.scm"
loading "~~/gsc/_front.scm"
loading "~~/gsc/_prims.scm"
loading "~~/gsc/_assert.scm"
loading "~~/gsc/_asm.scm"
loading "~~/gsc/_x86.scm"
loading "~~/gsc/_arm.scm"
loading "~~/gsc/_riscv.scm"
loading "~~/gsc/_codegen.scm"
loading "~~/gsc/_t-univ-1.scm"
loading "~~/gsc/_t-univ-2.scm"
loading "~~/gsc/_t-univ-3.scm"
loading "~~/gsc/_t-univ-4.scm"
loading "~~/gsc/_t-cpu-abstract-machine.scm"
loading "~~/gsc/_t-cpu-primitives.scm"
loading "~~/gsc/_t-cpu-object-desc.scm"
loading "~~/gsc/_t-cpu-utils.scm"
loading "~~/gsc/_t-cpu-backend-x86.scm"
loading "~~/gsc/_t-cpu-backend-arm.scm"
loading "~~/gsc/_t-cpu-backend-riscv.scm"
loading "~~/gsc/_t-cpu.scm"
loading "~~/gsc/_t-c-1.scm"
loading "~~/gsc/_t-c-3.scm"
loading "~~/gsc/_t-c-2.scm"
loading "~~/gsc/_gsclib.scm"
loading "~~/gsc/_gsc.scm"
loading "~~/gsc/_gscdebug.scm"
Gambit v4.9.3-1234-g6acd87df

>  (compile-file "c.scm")
"/home/lucier/programs/gambit/gambit/c.o1"

This is in the Gambit source directory after a build.

luca regini

@lucaregini

thanks @gambiteer this works also for me.

Bradley Lucier

@gambiteer

I'm curious: What will you do with the interpreted compiler?

luca regini

@lucaregini

I want to study the compiler internals and document them as far as I can. This is something that I wanted to do for quite some time. Being able to step into the code helps considerably.

Bradley Lucier

@gambiteer

Cool.

Guillaume Cartier

@gcartier

I have built Gambit on Windows 10 using mingw-w64 using the Mingw-builds installer and choosing architecture: x86_64, threads: posix, exception: seh (mimicking the configuration used by Marc in Gambit’s appveyor.yml) and all seems to work but I get quite frequent access violation crashes that all point to longjmp. Any idea anyone? Any trail would be helpful I have no idea where to go

Guillaume Cartier

@gcartier

Addendum: I just saw the commit: "Use gcc __builtin_setjmp when available” on Jun 13 2020 that seems to be exactly the fix for the crashes I encounter. I will try and build using the latest Gambit and see if it fixes my crashes. Will report the results :)

François-René Rideau

@fare

:hamster: Gerbil Scheme
♞ Gambit Scheme

Guillaume Cartier

@gcartier

With the commit "Use gcc __builtin_setjmp when available” I now have both the Mac and Windows crashing. I ended up fixing the crashes by building Gambit with —enable-cpluscplus

Erkin B Altunbaş

@erkin

Hello

Can you update the README file in the repo with the latest supported SRFIs?

Right now Gambit column on the SRFI support table is incomplete because it relies on files in libs/srfi instead, which aren't present in the last tagged version.

http://htmlpreview.github.io/?https://github.com/schemedoc/srfi-metadata/blob/master/table.html

It would be much easier to parse README for both head and tagged versions.

Erkin B Altunbaş

@erkin

I manually added details for Gambit for the time being.

Marc Feeley

@feeley

@erkin The SRFIs that are builtin are in the list returned by the R7RS procedurefeatures:

SRFI-0 SRFI-4 SRFI-6 SRFI-8 SRFI-9 SRFI-16 SRFI-18 SRFI-21 SRFI-22 SRFI-23 SRFI-27 SRFI-30 SRFI-39 SRFI-88

Gambit has some additional SRFIs implemented as modules that can be imported with import:

(import (srfi 28))  ;; Basic Format Strings
(import (srfi 41))  ;; Streams.
(import (srfi 64))  ;; A Scheme API for test suites
(import (srfi 69))  ;; Basic hash tables
(import (srfi 132)) ;; Sort Libraries
(import (srfi 158)) ;; Generators and Accumulators

I’ll look into how best to add that information to Gambit’s README.

Erkin B Altunbaş

@erkin

Thanks!

Currently, the scraper misses 16, 30 and 88.

James Baker

@eval-apply

Did anyone decipher why Gambit is producing erratic segfaults while doing a make modules? Seems to compile without issue using clang 10.0.1 albeit painfully slow but failing via gcc 8.3.0

Bradley Lucier

@gambiteer

Is it true in all Gambit back-ends that a valid vector index is a fixnum?

Marc Feeley

@feeley

@gambiteer yes