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

2nd CfP: SLE 2025 - 18th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis 20 Dec '24

20 Dec '24

18th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2025) 12-13 June 2025 Koblenz, Germany https://www.sleconf.org/2025/ https://x.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 18th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2025 conference will be co-located with STAF 2025 and hosted in Koblenz, Germany, on 12-13 June 2025. --------------------------- Important Dates --------------------------- * Abstract submission: Fri 7 Feb 2025 * Paper submission: Fri 14 Feb 2025 * Authors response period: Tue 1 Apr - Sat 5 Apr 2025 * Notification: Tue 15 Apr 2025 * Conference: Thu 12 June - Fri 13 June 2025 (co-located with STAF) All dates are Anywhere on Earth. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - AI-assisted language design and optimisation * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Model-based testing - AI-assisted validation * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - AI-assisted refactoring * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and emerging/promising research areas - Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) - AI and ML language engineering (e.g., ML compiler testing, code classification) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: * Research papers: These are “traditional” papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. * New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. * SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. * Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. Workshops: Workshops will be organised by STAF. Please inform us and contact STAF 2025 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2025 Website. --------------------------- Submission --------------------------- SLE 2025 has a single submission round for papers, including a mandatory abstract registration and a rebuttal phase, where all authors of research papers will have the possibility of responding to the reviews on their submissions. Authors of accepted research papers will be invited to submit artefacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format “acmart” ( https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is `\documentclass[sigplan,anonymous,review]{acmart}`. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authors’ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. The submission website is: https://sle25.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLAN’s Republication Policy ( https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACM’s Policy and Procedures on Plagiarism ( https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACM’s general principles, as stated in the ACM’s Publications Policy on Research Involving Human Participants and Subjects ( https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. SLEBoK papers will be reviewed on their soundness, relevance, originality, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. For research papers, authors will get a chance to respond to the reviews before a final decision is made. --------------------------- Artefact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. --------------------------- Awards --------------------------- * Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. * Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. * Most Influential Paper: Award for the SLE 2015 paper with the greatest impact, as judged by the SLE Steering Committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **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 the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- * General chair: Görel Hedin, Lunds Universitet, Sweden * PC co-chair: Regina Hebig, Universität Rostock, Germany * PC co-chair: Vadim Zaytsev, Universiteit Twente, The Netherlands * Publicity chair: Andrei Chiş, feenk gmbh, Switzerland * Local chair: Ralf Lämmel, Universität Koblenz, Germany --------------------------- Contact --------------------------- For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs (regina.hebig(a)uni-rostock.de and vadim(a)grammarware.net)

1 0

[TFP (and TFPiE) 2025] Call For Participation (January 13-16, Oxford, UK)
by Peter Achten 18 Dec '24

18 Dec '24

TFP 2025 -- Call For Participation (trendsfp.github.io) Venue TFPiE and TFP will take place in-person in the Wolfson Building of the Department of Computer Science at the University of Oxford. Dates Early registration: December 20, 2024 Late registration: January 6, 2025 TFPiE Workshop: Monday 13th January, 2025 TFP Symposium: Tuesday 14th - Thursday 16th January, 2025 The Symposium on Trends in Functional Programming (TFP) is an international forum for researchers with interests in all aspects of functional programming, taking a broad view of current and future trends in the area. It aspires to be a lively environment for presenting the latest research results, and other contributions. Keynote speakers We are happy to have the following keynotes in the programme: * Nicolas Wu (TFPiE), Imperial College London: "Fractal Foundations and Galactic Graphs: Structure and Strategy for Expanding Minds" * Graham Nelson, University of Oxford: "Literate Programming and Cultural Practice" * Mike Sperber, Active Group: "Things We Never Told Anyone About Functional Programming" * Kathrin Stark, Heriot-Watt University: "A Verified Foreign Function Interface Between Coq and C" Programme We have 28 paper presentations. The programme schedule can be found here: trendsfp.github.io/schedule.html Excursion and banquet In the afternoon and evening of Wednesday January 15th we have an excursion to the History of Science Museum. We have a break in a cosy pub, before proceeding to Kellogg College for the conference banquet. During dinner the winners of the best paper awards of last year's TFP are announced.

1 0

How to build and test big-endian Gambit Scheme on Ubuntu x86-64
by Bradley Lucier 05 Dec '24

05 Dec '24

I just went through this exercise for my own purposes, thought some of you might be interested. It's certainly easier than trying to find and maintain sparc/ppc/mips hardware/software. 1. Install MIPS compiler and runtime library, and qemu-mips: 1 18:23 sudo apt-get install gcc-multilib-mips-linux-gnu 3 18:26 sudo apt-get install gcc-mips-linux-gnu 5 18:26 sudo apt-get install qemu-user 2. Clone Gambit, build boot/ and gsc-boot: 9 18:28 git clone https://github.com/gambit/gambit.git 10 18:28 cd gambit 11 18:28 ./configure 12 18:29 make -j8 core 3. Reconfigure Gambit to build a cross-compiled MIPS version: 15 18:35 ./configure --host=mips-linux-gnu 4. Build a MIPS gsi/gsi and gsc/gsc: 16 18:35 make clean 18 18:36 make -j8 core 5. Test gsi/gsi with qemu-mips, telling qemu-mips where to find MIPS version of ld.so.1: 49 18:56 qemu-mips -L /usr/mips-linux-gnu/ gsi/gsi 6. Run a unit test: 69 19:14 qemu-mips -L /usr/mips-linux-gnu/ gsi/gsi tests/unit-tests/03-number/_num.scm 7. Check that it really is a MIPS binary: 72 19:22 file gsi/gsi Output: gsi/gsi: ELF 32-bit MSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked, interpreter /lib/ld.so.1, BuildID[sha1]=c434b85ac605107cc0a7d45ba0f12e70243113ca, for GNU/Linux 3.2.0, not stripped 8. Get some silly timings: heine:~/programs/gambit/big-endian/gambit> qemu-mips -L /usr/mips-linux-gnu/ gsi/gsi Gambit v4.9.5-206-g42e51d68 > (define a (time (expt 3 1000000)))(define b (time (* a a))) (time (expt 3 1000000)) 0.879048 secs real time 0.877924 secs cpu time (0.876923 user, 0.001001 system) 3 collections accounting for 0.003398 secs real time (0.003400 user, 0.000001 system) 3257548 bytes allocated 1930 minor faults no major faults > (time (* a a)) 0.973768 secs real time 0.972830 secs cpu time (0.972827 user, 0.000003 system) 1 collection accounting for 0.001181 secs real time (0.001180 user, 0.000001 system) 4524200 bytes allocated 2055 minor faults no major faults The corresponding native binary: heine:~/programs/gambit/big-endian/gambit> gsi Gambit v4.9.5-204-g79fcaed1 > (define a (time (expt 3 1000000)))(define b (time (* a a))) (time (expt 3 1000000)) 0.018802 secs real time 0.016549 secs cpu time (0.015181 user, 0.001368 system) 2 collections accounting for 0.000659 secs real time (0.000591 user, 0.000070 system) 3295704 bytes allocated 1764 minor faults 1 major fault 67505646 cpu cycles > (time (* a a)) 0.016171 secs real time 0.016149 secs cpu time (0.013784 user, 0.002365 system) 1 collection accounting for 0.000319 secs real time (0.000000 user, 0.000319 system) 4524224 bytes allocated 2050 minor faults no major faults 58058052 cpu cycles And I added -save-temps to the makefile command to compile lib/_num.c to see that yes, this really is a big-endian version of _num.i. Pretty cool! Brad

1 0