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

Problem building on Catalina
by hashavtech＠outlook.com 08 Jul '20

08 Jul '20

For some time, I'm having trouble compiling Gambit with SMP on Mac (running Catalina 10.15.4). I've tried with the Apple's clang, I've installed several compilers through Macports, several versions of gcc and clang and I have the same problem: segmentation faults during make modules. Source is from git master, but I've tried going a few months back with no luck. I'm running configure as ./configure --enable-single-host --enable-multiple-versions --enable-multiple-threaded-vms --enable-smp --enable-targets=js (If I leave out one of the --enable-multiple-threaded-vms or --enable-smp flags then it builds ok) and after the make -j && make modules I see stuff like this (in different modules): >>>> building module _match for C >>>> building module _match/match-expand for C /bin/sh: line 7: 65949 Segmentation fault: 11 ../../gsc/gsc -:~~bin=../../bin,~~lib=../../lib,~~include=../../include -f -e "(let ((x (##build-module \"$main_mod\" (quote $target) (quote ((module-ref $modref)))))) (if (not x) (begin (println \"*** module failed to build\") (exit 1))))" or >>>> building module _test/verbose for js /bin/sh: line 7: 66835 Segmentation fault: 11 ../../gsc/gsc -:~~bin=../../bin,~~lib=../../lib,~~include=../../include -f -e "(let ((x (##build-module \"$main_mod\" (quote $target) (quote ((module-ref $modref)))))) (if (not x) (begin (println \"*** module failed to build\") (exit 1))))" Not sure how relevant this is, but if I build Gambit using --enable-smp but without --enable-multiple-threaded-vms, I get a successful build, but then I have one failed test when running make check: [226| 0] 90% ##############.. 10.3s 13-modules/prim_exception.scm *** FAILED 13-modules/prim_exception.scm WITH EXIT CODE HI=1 LO=0 (with-exception-handler ##list (lambda () (##cons 1 (##raise 123)))) in (include "~~lib/gambit/prim/exception#.scm") returned #<unbound-global-exception #2> but expected (1 123) (with-exception-handler ##list (lambda () (##cons 1 (##raise 123)))) in (namespace ("##")) returned #<unbound-global-exception #3> but expected (1 123) [250| 1] 100% ################ 11.3s FAILED 1 UNIT TESTS OUT OF 251 (.4%) gmake[2]: *** [makefile:186: ut] Error 1 gmake[2]: Leaving directory '/Users/ury/sources/gambit/tests' gmake[1]: *** [makefile:183: test11] Error 2 gmake[1]: Leaving directory '/Users/ury/sources/gambit/tests' gmake: *** [makefile:208: check] Error 2 Maybe this problem sounds familiar, or at least maybe there is something I can try to fix or at least to debug it? (This is on an old Macbook, so I would've suspected faulty hardware, but I've tried some rather significant builds such as GTK3 or TeX and they run ok) I'm attaching the full compilation log (this time with GCC 10, but I had the same results with other versions).

1 0

Any research on improving Lisp/Scheme error messages?
by Lassi Kortela 05 Jul '20

05 Jul '20

One of the shortcomings of current Scheme and Lisp implementations is that error messages can be intimidating to newcomers and confuse even experienced programmers from time to time. Has there been any academic research on friendlier error messages? A quick Google Scholar search does not turn up any papers.

1 0

Call for Tutorial Proposals: ICFP 2020
by Sam Tobin-Hochstadt 17 Jui '20

17 Jui '20

CALL FOR TUTORIAL, PANEL, AND DISCUSSION PROPOSALS ICFP 2020 25th ACM SIGPLAN International Conference on Functional Programming August 23 - 28, 2020 Virtual https://icfp20.sigplan.org/ The 25th ACM SIGPLAN International Conference on Functional Programming will be held virtually on August 23-28, 2020. ICFP provides a forum for researchers and developers to hear about the latest work on the design, implementations, principles, and uses of functional programming. Proposals are invited for tutorials, lasting approximately 3 hours each, to be presented during ICFP and its co-located workshops and other events. These tutorials are the successor to the CUFP tutorials from previous years, but we also welcome tutorials whose primary audience is researchers rather than practitioners. Tutorials may focus either on a concrete technology or on a theoretical or mathematical tool. Ideally, tutorials will have a concrete result, such as "Learn to do X with Y" rather than "Learn language Y". This year, following the success of the #ShutDownPL event, we are also inviting proposals for panels and discussions on topics of broader interest to the PL community. Tutorials, panels, and discussions may occur before or after ICFP, co-located with the associated workshops, on August 23 or August 27-28. ---------------------------------------------------------------------- Submission details Deadline for submission: July 17th, 2020 Notification of acceptance: July 22nd, 2020 Prospective organizers of tutorials are invited to submit a completed tutorial proposal form in plain text format to the ICFP 2020 workshop co-chairs (Jennifer Hackett and Leonidas Lampropoulos), via email to icfp-workshops-2020(a)googlegroups.com by July 17th, 2020. Please note that this is a firm deadline. Organizers will be notified if their event proposal is accepted by July 22nd, 2020. The proposal form is available at: http://www.icfpconference.org/icfp2020-files/icfp20-panel-form.txt http://www.icfpconference.org/icfp2020-files/icfp20-tutorials-form.txt ---------------------------------------------------------------------- Selection committee The proposals will be evaluated by a committee comprising the following members of the ICFP 2020 organizing committee. Tutorials Co-Chair: Jennifer Hackett (University of Nottingham) Tutorials Co-Chair: Leonidas Lampropoulos (University of Maryland) General Chair: Stephanie Weirich (University of Pennsylvania) Program Chair: Adam Chlipala (MIT) ---------------------------------------------------------------------- Further information Any queries should be addressed to the tutorial co-chairs (Jennifer Hackett and Leonidas Lampropoulos), via email to icfp-workshops-2020(a)googlegroups.com

1 0

Re: [gambit-list] fix in dem letzten Beispiel
by Jörg F. Wittenberger 10 Jui '20

10 Jui '20

Kann das sein, daß da der Port 9993 schon durch 'wen anderes belegt ist? (Hast Du vllt. das zerotier-one installiert? netstat -l -u -p Beim hier ausprobieren habe ich noch zwei Fehler entdeckt, denn einen in Deiner Zeile: nach dem "join:" muß ein Leerzeichen kommen. Den anderen im Code, gibt man ein nicht existierendes Verzeichnis an, dann wurde bis eben "#unbound" gerufen. Da fehlte ein "!" hinter dem "set". Nur zur Sicherheit, daß Du auf dem aktuelle Stand testest schick' ich Dir das binary neu mit. Du kannst nicht zwei Prozesse an den selben Port auf dem selben Interface binden. Mit 'nem anderen Port sollte das gehen. On Tue, 9 Jun 2020 21:56:17 +0200 Steffen Rietz <steffen_rietz(a)gmx.de> wrote: > Das Kommando: > ot0 -B ottest -adm ip: on -S control 9090 : -S ot0 start '"*:9993"' > join:18382870269589979136 -repl > > liefert: > *** ERROR IN %ot0cli-ot-wire-packet-send -- (Argument 1) Can't > convert to C struct (udp-destination-set! > '#u8(36 0 97 128 0 0 0 208 0 183 64 1 8 254 204 8) > 9993 > '#<input-output-port #11 (udp "*" 9993)>) > > Gesendet: Dienstag, 09. Juni 2020 um 11:24 Uhr > Von: "Jörg F. Wittenberger" <Joerg.Wittenberger(a)softeyes.net> > An: "Steffen Rietz" <steffen_rietz(a)gmx.de> > Betreff: fix in dem letzten Beispiel > >

1 1

First call for draft papers for IFL 2020 (Implementation and Application of Functional Languages)
by Jurriaan Hage 08 Jui '20

08 Jui '20

Hello, Please, find below the final call for draft papers for IFL 2020. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL ================================================================================ IFL 2020 32nd Symposium on Implementation and Application of Functional Languages venue: online 2nd - 4th September 2020 https://www.cs.kent.ac.uk/events/2020/ifl20/ ================================================================================ ### Scope The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2020 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Topics of interest to IFL include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialisation - run-time code generation - partial evaluation - (abstract) interpretation - meta-programming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications ### Post-symposium peer-review Following IFL tradition, IFL 2020 will use a post-symposium review process to produce the formal proceedings. Before the symposium authors submit draft papers. These draft papers will be screened by the program chair to make sure that they are within the scope of IFL. The draft papers will be made available to all participants at the symposium. Each draft paper is presented by one of the authors at the symposium. After the symposium every presenter is invited to submit a full paper, incorporating feedback from discussions at the symposium. Work submitted to IFL may not be simultaneously submitted to other venues; submissions must adhere to ACM SIGPLAN's republication policy. The program committee will evaluate these submissions according to their correctness, novelty, originality, relevance, significance, and clarity, and will thereby determine whether the paper is accepted or rejected for the formal proceedings. We plan to publish these proceedings in the International Conference Proceedings Series of the ACM Digital Library, as in previous years. ### Important dates Submission deadline of draft papers: 17 August 2020 Notification of acceptance for presentation: 19 August 2020 Registration deadline: 31 August 2020 IFL Symposium: 2-4 September 2020 Submission of papers for proceedings: 7 December 2020 Notification of acceptance: 3 February 2021 Camera-ready version: 15 March 2021 ### Submission details All contributions must be written in English. Papers must use the ACM two columns conference format, which can be found at: http://www.acm.org/publications/proceedings-template ### Peter Landin Prize The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honoured article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. ### Organisation IFL 2020 Chair: Olaf Chitil, University of Kent, UK IFL Publicity chair: Jurriaan Hage, Utrecht University, The Netherlands ### Virtual symposium Because of the Covid-19 pandemic, this year IFL 2020 will be an online event, consisting of paper presentations, discussions and virtual social gatherings. Registered participants can take part from anywhere in the world. ### Acknowledgments This call-for-papers is an adaptation and evolution of content from previous instances of IFL. We are grateful to prior organisers for their work, which is reused here.

1 0

Call for Submissions: ICFP Student Research Competition
by Sam Tobin-Hochstadt 02 Jui '20

02 Jui '20

ICFP 2020 Student Research Competition Call for Submissions ICFP invites students to participate in the Student Research Competition, which will be held virtually alongside the main conference, in order to present their research and receive feedback from prominent members of the programming language research community. As usual, the SRC consists of three rounds: * Extended abstract * Poster session at ICFP 2020 * ICFP presentation To make the virtual competition fruitful, we will make sure that every student will have an "invited audience" during the poster session. We are also planning to organize a social event for the students. Please visit the SRC website for updates. ### Important Dates Submissions due: 26 Jun 2020 (Friday) https://icfp20src.hotcrp.com Notification: 10 July 2020 (Friday) Conference: 23 August (Sunday) - 28 August (Friday) ### Submission Details Each submission (referred to as "abstract" below) should include the student author’s name and e-mail address; institutional affiliation; research advisor’s name; ACM student member number; category (undergraduate or graduate); research title; and an extended abstract addressing the following: * Problem and Motivation: Clearly state the problem being addressed and explain the reasons for seeking a solution to this problem. * Background and Related Work: Describe the specialized (but pertinent) background necessary to appreciate the work in the context of ICFP areas of interest. Include references to the literature where appropriate, and briefly explain where your work departs from that done by others. * Approach and Uniqueness: Describe your approach in addressing the problem and clearly state how your approach is novel. * Results and Contributions: Clearly show how the results of your work contribute to programming language design and implementation in particular and to computer science in general; explain the significance of those results. * Submissions must be original research that is not already published at ICFP or another conference or journal. One of the goals of the SRC is to give students feedback on ongoing, unpublished work. Furthermore, the abstract must be authored solely by the student. If the work is collaborative with others and*or part of a larger group project, the abstract should make clear what the student’s role was and should focus on that portion of the work. * Formatting: Submissions must be in PDF format, printable in black and white on US Letter sized paper, and interpretable by common PDF tools. All submissions must adhere to the "ACM Small" template that is available (in both LaTeX and Word formats) from https://www.acm.org/publications/authors/submissions. For authors using LaTeX, a lighter-weight package, including only the essential files, is available from http://sigplan.org/Resources/Author/#acmart-format. The submission must not exceed 3 pages in PDF format. Reference lists do not count towards the 3-page limit. Further information is available at the ICFP SRC website: https://icfp20.sigplan.org/track/icfp-2020-Student-Research-Competition Program Committee: Chair: Youyou Cong (Tokyo Institute of Technology) Stephen Chang (University of Massachusetts Boston) Jesper Cockx (Delft University of Technology) Hsiang-Shang Ko (Institute of Information Science, Academia Sinica) Cyrus Omar (University of Michigan)

1 0

Comparing a 2020 iPhone SE to a 7-year-old Linux box
by Bradley Lucier 24 Mai '20

24 Mai '20

The Linux box is running Ubuntu 18.04 with model name : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz and Gambit was compiled with v4.9.3-1111-g05060cf0 20200521224855 x86_64-pc-linux-gnu "./configure 'CC=/usr/local/gcc-10.1.0/bin/gcc -march=native -D___CAN_IMPORT_CLIB_DYNAMICALLY' '--enable-strict-aliasing' '--enable-single-host' '--enable-shared' '--enable-multiple-versions'" The iPhone SE is running the Gambit REPL app, based on Gambit 4.7.4. The comparison is very simple, I run gsi -e '(define a (time (expt 3 100000000)))(pp (time (integer-length (* a a))))' (time (expt 3 100000000)) 2.663234 secs real time 2.633248 secs cpu time (2.434250 user, 0.198998 system) 8 collections accounting for 0.020154 secs real time (0.006686 user, 0.012848 system) 1210688 bytes allocated 272088 minor faults no major faults (time (integer-length (* a a))) 2.877121 secs real time 2.869723 secs cpu time (2.665860 user, 0.203863 system) 1 collection accounting for 0.019379 secs real time (0.000000 user, 0.018940 system) 85536 bytes allocated 272140 minor faults no major faults 316992501 on the Linux box, the times on the iPhone SE are 2.759 seconds for the first computation and 2.990 seconds for the second. If I look at an older build of Gambit on the Linux box, with v4.9.1 20180930122740 x86_64-unknown-linux-gnu "./configure 'CC=gcc -march=native -D___CAN_IMPORT_CLIB_DYNAMICALLY' '--enable-single-host' '--enable-shared' '--enable-multiple-versions'" i.e., with an older compiler and without --enable-strict-aliasing, then I see gsi -e '(define a (time (expt 3 100000000)))(pp (time (integer-length (* a a))))' (time (expt 3 100000000)) 3.328249 secs real time 3.327808 secs cpu time (3.103869 user, 0.223939 system) 8 collections accounting for 0.019851 secs real time (0.004052 user, 0.015809 system) 1213248 bytes allocated 272088 minor faults no major faults (time (integer-length (* a a))) 3.572195 secs real time 3.571591 secs cpu time (3.335618 user, 0.235973 system) 1 collection accounting for 0.020848 secs real time (0.000757 user, 0.020061 system) 85536 bytes allocated 272140 minor faults no major faults 316992501 i.e., the iPhone is undeniably faster. I heard a rumor that Apple will start shipping Arm-based Macbook laptops with CPUs of its own design, maybe not the Macbook Pros, just the Macbook Airs. That certainly doesn't look unreasonable. Brad

2 1

[CfP] DLS 2020 - Dynamic Languages Symposium, submission deadline July 9th
by Matthew Flatt 18 Mai '20

18 Mai '20

The 16th Dynamic Languages Symposium (DLS) at SPLASH 2020 is the premier forum for researchers and practitioners to share research and experience on all aspects on dynamic languages. DLS 2020 invites high quality papers reporting original research and experience related to the design, implementation, and applications of dynamic languages. Areas of interest include, but are not limited to, - innovative language features - innovative implementation techniques - innovative applications - development environments and tools - experience reports and case studies - domain-oriented programming - late binding, dynamic composition, and run-time adaptation - reflection and metaprogramming - software evolution - language symbiosis and multi-paradigm languages - dynamic optimization - interpretation - just-in-time and ahead-of-time compilation - soft/optional/gradual typing - hardware support - educational approaches and perspectives - semantics of dynamic languages - frameworks and languages for the Cloud and the IoT Submission Details ------------------ Submissions must neither be previously published nor under review at other events. DLS 2020 uses a lightweight double-blind, two-phase reviewing process. Papers are assumed to be in one of the following categories: **Research Papers:** describe work that advances the current state of the art **Experience Papers:** describe insights gained from substantive practical applications that should be of a broad interest **Dynamic Pearls:** describe a known idea in an appealing way to remind the community and capture a reader’s interest The program committee will evaluate each paper based on its relevance, significance, clarity, and originality. The paper category needs to be indicated during submission, and papers are judged accordingly. Papers are to be [submitted electronically](https://dls20.hotcrp.com/) in PDF format. Submissions must be in the ACM SIGPLAN conference acmart format, 10 point font, and should not exceed 12 pages. Please see full details in the instructions for authors available at: https://conf.researchr.org/home/dls-2020#Instructions-for-Authors DLS 2020 will run a two-phase reviewing process to help authors make their final papers the best that they can be. Accepted papers will be published in the ACM Digital Library and will be freely available for one month, starting two weeks before the event. ## Important Deadlines Abstract Submission (optional): July 2, 2020 Paper Submission: July 9, 2020 First Phase Notification: August 7, 2020 Revisions Due: September 4, 2020 Final Notifications: Septemberr 18, 2020 All deadlines are 23:59 AoE (UTC-12h). **AUTHORS TAKE NOTE:** The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. Program Committee ----------------- Alexandre Bergel, U Chile Shigeru Chiba, U Tokyo Stéphane Ducasse, Inria Tim Felgentreff, HPI Matthew Flatt, U Utah (chair) Elisa Gonzalez Boix, VUB Michael Homer, Victoria U Wellington Mark Marron, Microsoft Research Anders Møller, Aarhus Manuel Rigger, ETH Sukyoung Ryu, KAIST Jeremy G. Siek, Indiana U Francesco Zappa Nardelli, Facebook

1 0

newbie: bitwise and arithmetic runtime speed for u64
by Paolo Montrasi 17 Mai '20

17 Mai '20

Hi all, As a learning exercise, I am experimenting in chess/alpha-beta search/bitboards. In this domain lot of bitwise operations are required. My goal is to keep learning scheme and Gambit, therefore I will be happy to stay with what I have right now if the only option is to switch to C et similia. I am asking here for an advice in improving runtime speed crunching bitwise operations on u64 integers since I have no experience using scheme and Gambit. Looking at the documentation I see that fixnum is providing some help but I apparently u64 integers are not "compatible" with fixnum operations > (fixnum? 18446744073709551615) #f Can you share suggestions for my next exercise? Thank you in advance Paolo

6 9

Gerbil v0.16 is out!
by Dimitris Vyzovitis 17 Mai '20

17 Mai '20

Hi all, I am happy to announce the release of Gerbil v0.16. Release Highlights: - R7RS Tangerine, Polydactyl Gerbil, Class Sealing and more. - Overhauled std/make library and parallelized builds. - Configure and install scripts. - Overhauled documentation, with a beautiful new logo! - A new Gitter chat room at https://gitter.im/gerbil-scheme/community As usual, for sources and downloads: https://github.com/vyzo/gerbil https://github.com/vyzo/gerbil/releases Full release changelog: https://github.com/vyzo/gerbil/blob/master/CHANGELOG.md For questions and support, come say hi on Gitter or irc at #gerbil-scheme in irc.freenode.net. Happy Hacking! -- vyzo

1 0