- Gambit-list - mailman.iro.umontreal.ca

inlining eqv? etc.
by Bradley Lucier 13 Oct '06

13 Oct '06

Marc: I'm going over c#prim-procs to see which other routines could be inlined. First, I'm comparing (##define-macro (macro-number-dispatch num err fix big rat flo cpx) `(cond ((##fixnum? ,num) ,fix) ((##flonum? ,num) ,flo) ((##subtyped? ,num) (let ((##s (##subtype ,num))) (cond ((##fixnum.= ##s (macro-subtype-bignum)) ,big) ((##fixnum.= ##s (macro-subtype-ratnum)) ,rat) ((##fixnum.= ##s (macro-subtype-cpxnum)) ,cpx) (else ,err)))) (else ,err))) in _num#.scm with (define-prim (##flonum? obj) (and (##subtyped? obj) (##eq? (##subtype obj) (macro-subtype-flonum)))) in sys.scm, and I suggest macro-number-dispatch be redefined as (##define-macro (macro-number-dispatch num err fix big rat flo cpx) `(cond ((##fixnum? ,num) ,fix) ((##subtyped? ,num) (let ((##s (##subtype ,num))) (cond ((##fixnum.= ##s (macro-subtype-flonum)) ,flo) ((##fixnum.= ##s (macro-subtype-bignum)) ,big) ((##fixnum.= ##s (macro-subtype-ratnum)) ,rat) ((##fixnum.= ##s (macro-subtype-cpxnum)) ,cpx) (else ,err)))) (else ,err))) Now, I look at (define-prim (##eqv? obj1 obj2) (macro-number-dispatch obj1 (##eq? obj1 obj2) (and (##fixnum? obj2) (##fixnum.= obj1 obj2)) ; obj1 = fixnum (and (##bignum? obj2) (##bignum.= obj1 obj2)) ; obj1 = bignum (and (##ratnum? obj2) (##ratnum.= obj1 obj2)) ; obj1 = ratnum (and (##flonum? obj2) (##bvector-equal? obj1 obj2)) ; obj1 = flonum (and (##cpxnum? obj2) ; obj1 = cpxnum (##eqv? (macro-cpxnum-real obj1) (macro-cpxnum-real obj2)) (##eqv? (macro-cpxnum-imag obj1) (macro-cpxnum-imag obj2))))) in sys.scm. I think one can (should?) inline (##eqv? x y) as (or (##eq? x y) (and (##subtyped? x) (##subtyped? y) (let ((##sx (##subtype x))) (and (##fixnum.= ##sx (##subtype y)) (or (##fixnum.= ##sx (macro-subtype-flonum)) (##fixnum.= ##sx (macro-subtype-bignum)) (##fixnum.= ##sx (macro-subtype-ratnum)) (##fixnum.= ##sx (macro-subtype-cpxnum))) (##eqv? x y))))) The second limb of the first "or" can be be eliminated for many compile-time constants (please use the commutativity of ##eqv? if y happens to be a compile-time constant and x isn't), which can be especially important for compiling "case" forms. There are a number of "case" forms in the files compiler, dynamic, early, graphs, lattice, matrix, nboyer, nucleic, sboyer, scheme, and test in bench/src. In your latest benchmarks Bigloo beat Gambit in boyer, dynamic, and scheme; maybe the lack of inlining of eqv? in case contributed. Perhaps one can use a similar strategy for inlining equal? Other things that could (should?) be inlined (perhaps some of these already are inlined for special values of the arguments): boolean? list-ref (like memv) memv (now that eqv? can be inlined) assv (ditto) number?, complex?, real?, rational?, integer?, exact?, inexact? (it doesn't seem so bad to inline macro-number-dispatch since the results are boolean, or at least these could be tested for fixnum and flonum) abs (for fixnum, using ##fixnum.-? if the argument is negative) gcd and lcm (for one argument) numerator and denominator (for fixnums) floor, ceiling, truncate, round (for fixnums) real-part, imag-part, magnitude (for fixnum and flonum arguments) string string=? and friends with 0 and 1 arguments. Generally, I went through all the items in prim-procs, and generated little programs that used them with varying number of arguments, then visually inspected the expanded code and (sometimes) the C code to see what's going on. I'm including my little test file at the end. Brad

2 5

SSAX
by Aycan iRiCAN 10 Oct '06

10 Oct '06

Hi, Is it possible to use SSAX with gambit? Anyone using it? After running "make SSAX-code.scm" I tried to load it: > (load "~/scheme/SSAX/lib/SSAX.scm") *** ERROR IN "../../../SSAX/lib/SSAX.scm"@307.16 -- Ill-placed 'define' Note: SSAX cvs. Best Regards, -- Aycan iRiCAN C0R3 Computer Security Group http://people.core.gen.tr/~aycan.irican/

4 3

equal greater symbol
by Aycan iRiCAN 09 Oct '06

09 Oct '06

Hi, What is the meaning of '=> symbol used in cond forms? Best Regards, -- Aycan iRiCAN C0R3 Computer Security Group http://people.core.gen.tr/~aycan.irican/

3 2

example web server
by Aycan iRiCAN 08 Oct '06

08 Oct '06

Hi, I start the web-server example with the command: gsi html http web-server 8000 after that, web continuation example gives error: The following Scheme exception occurred while processing the request: Unbound variable: base64#u8vector->base64-string I think it should be started with a command like this: gsi base64 html http web-server 8000 The README file in web-server example needs to be updated. Best Regards, -- Aycan iRiCAN C0R3 Computer Security Group http://people.core.gen.tr/~aycan.irican/

2 1

Gambit-C 4.0 beta 20
by Marc Feeley 07 Oct '06

07 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gambit-C 4.0 beta 20 is now available. The source tarball is here: <http://www.iro.umontreal.ca/~gambit/download/gambit/4.0/source/ gambc-4.0b20.tar.gz> A prebuilt installation for Microsoft Windows is available here: <http://www.iro.umontreal.ca/~gambit/download/gambit/4.0/prebuilt/ gambc-4.0b20-win.zip> Just unzip it in C: to get C:\Gambit-C\4.0b20, then add C:\Gambit-C\4.0b20\bin to your path. Here are the highlights of this release: - The mutation procedures (set-car!, set-cdr!, vector-set!, string-set!, etc) now check that the object is mutable (not a constant). For example: Gambit Version 4.0 beta 20 > (define x (symbol->string 'hello)) > (string-set! x 0 #\m) *** ERROR IN (console)(a)2.1 -- (Argument 1) MUTABLE object expected (string-set! "hello" 0 #\m) - The compiler, gsc, now produces dynamically loadable object files by default. The -dynamic flag is thus optional. To generate a link file (which used to be the default) you must use the -link option. - The GCC compilation options used for Gambit have been updated to improve the code generation (execution time is 5% to 30% faster than before). The set of compilation options was obtained by a genetic algorithm. - The --enable-gcc-opts configure option has been added. It enables some expensive GCC optimizations (the build time more than doubles and you need lots of RAM, i.e. 2 gigabytes or more). - Minor bug fix in the reader which treated #\ 123 as a syntax error instead of #\space followed by 123. - The runtime source code (in C) has been reorganized to be able to build Gambit on systems that are neither POSIX or WIN32. In this case the Gambit runtime will not include functionality such as networking, processes, and preemptive multithreading. It will use (blocking) stdio to do all I/O (presumably nearly all platforms, even embedded systems, have some library for stdio even if it is just a minimal functionality such as directing stdin/stdout to a serial port). Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFFJm2y//V9Zc2T/v4RAkuTAJ0Vctr2zwPHys7QEnEo2tNG5yqB4QCeNNQI 2/pVeYwzS8vnLnOwy1/Dgec= =xK9g -----END PGP SIGNATURE-----

2 2

Question from Newbie
by Sen, Suchira 05 Oct '06

05 Oct '06

Hi, I am new to gambit and am trying to write a journal file. I need to create an array to store strings, When I use the foll: declare $cve[1:3], and try to enter a string variable Ex. $cve[1]="vertex." - I find that the array cve is marked as an array of 'unknown type'. And the variables stored in it are also marked similarly. But if I sya $cve[1]=1, then it happily assigns a numeric value to it. So my question is how do we declare an array to be a character type? Thanks, Suchira.

1 0

Re: [gambit-list] strange mutation problem (bug?) (Re: "Number of arguments exceeds implementation)
by Christian 03 Oct '06

03 Oct '06

At 1:17 Uhr -0500 29.09.2006, Bill Richter wrote: >Christian suggested I might have found a real bug, The interesting bit is, that using compile-file & load Bill's program usually works, whereas with static compilation/linking not. I don't know where Gambit would differ in those two >and that I should >try stripping off as much fat as possible from my program. You should strip it more until you can say "if I leave this out, it doesn't do weird things anymore". Here's what you should be doing in such cases: * check which functions are really mutating, and which ones are functions. I realize that you're using map (meant for functions) where I think for-each (meant for imperative code) is what you want (maybe the order of evaluation may be a problem!). I realize that UnSpace clearly does mutate it's argument, thus rename it to UnSpace!. * try to find out whether ShowPossibilities mutates it's argument. From a quick look at the code, I'd say so, but runnning it in gsi, I couldn't find a modification of it's input, strange. * try to find out where during the runtime of the program the problem happens. For this, outputting the relevant datastructures helps. I've put a (pp U7) between the two ShowPossibilities calls and another one after the second. After the first ShowPossibilities call U7 is containing lists (is this what you want?); then the second ShowPossibilities call runs into the error. So clearly U7 has been modified, and ShowPossibilities should be renamed to ShowPossibilities!. Why does the same not happen in the interpreter? Before knowing that it's a Gambit bug, we have to rule out that it's from a difference between interpreter and compiler behaviour. Trimming it further down for an hour, I realize that you're modifying quoted datastructures. IIRC, R5RS says that modifying constant datastructures is undefined, and Gambit seems to rely on them not beeing modifyed when compiling to static binaries. Replace all quoted #(..) with (vector ..) and it works. Christian.

3 4

Re: [gambit-list] Prebuilt windows installation not available
by Marc Feeley 03 Oct '06

03 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2-Oct-06, at 4:37 AM, Tom Ayerst wrote: > Hi, > > I only have access to Windows machines at the moment but the > Prebuilt windows installation of Gambit 4.0 seems to be missing. > Is this a temorary thing? > > Thanks > > Tom Ayerst Indeed the prebuilt beta 18 for Windows was moved. In any case you want beta 19 which fixes an important bug in beta 18: http://www.iro.umontreal.ca/~gambit/download/gambit/4.0/prebuilt/ gambc-4.0b19-win.zip If you really want beta 18, just replace 19 by 18... Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFFIR+3//V9Zc2T/v4RAl3/AKCmece62XMiDuGzPbjNrLd5TsyIfwCgi5Mc Qs+B/pdT9NR0RrXPP1rU1Lk= =uFf+ -----END PGP SIGNATURE-----

4 4

ERROR IN ##parameterize
by Blake McBride 03 Oct '06

03 Oct '06

Greetings, I want to build a stand-alone (requiring no DLL's) scheme app under Windows. I re-built Gambit 4.0b19 with Microsoft VC without a problem. However, when I try to compile a trivial program I get: C:\Systems\Scheme\Gambit>gsc a.scm *** ERROR IN ##parameterize -- No such file or directory (current-directory "C:\\lib") C:\Systems\Scheme\Gambit>gsc -dynamic a.scm *** ERROR IN ##parameterize -- No such file or directory (current-directory "C:\\bin") a.scm just contains: (display "hello world") I tried the -verbose option and that gave me nothing useful. It would be unbelievably great if the -verbose option displayed the full compile and link commands it was running. I have no idea what that error message is trying to tell me. I tried all sorts of -cc-options and -ld-option options with no luck. Without a display of what it's executing, I'm in the dark. I'd prefer to use VC. Thanks. Blake McBride

2 4

mutating constant data (Re: strange mutation problem (bug?))
by Christian 29 Sep '06

29 Sep '06

I wrote: >Replace all quoted #(..) with (vector ..) Marc: From my experience with compile-file, Gambit is "copying" (or maybe rather constructing) data from constant definitions upon startup, with the nice benefit that it behaves like in the interpreter (e.g. insensitive to mutation). My guess is that Gambit is still doing the same in static binaries, but the copied/constructed data is allocated as ___PERM objects; thus storing non-immediate objects into them will not segfault right away, but the latter are not seen anymore by the GC, and hence when accessing the data after the next collection then points into undefined places in memory. Do you think it would be feasible to make mutating accessors throw an error in safe mode if their argument is a ___PERM object? (Or maybe it's cheaper to just use normal allocations?) I think I'm aware of the implications myself and won't write code which defines and mutates such data, but I may run into such issues again when working with other programmers (where one doesn't always realize the intents of the others). Christian.

1 0