clasp-devel

clasp-devel@common-lisp.net

30 discussions

CDR for Package-Local Nicknames [Feedback Request]
by Alexander Fedorov 06 Jul '24

06 Jul '24

Dear all, Over 10 years ago, SBCL implemented the Package-Local Nicknames (PLNs) extension. Since then, PLNs have also been adopted by multiple implementations (ABCL, CCL, ECL, Clasp, Allegro CL and LispWorks) and are now widely used in many projects. However, PLNs are still considered experimental, as stated in the SBCL manual, since there is no formal specification for them, and each implementation interprets various corner cases differently. While the need for a specification has been previously discussed, I was unable to find any publicly accessible draft for one. Therefore, I have drafted a specification intended to become a CDR document. I initially wrote this draft about a year ago and have recently revised it. You can find the latest version here: https://gleefre.github.io/cdr-package-local-nicknames/index.html. There are currently nine unresolved standardization issues, each with at least one proposed resolution. Input on those issues would be particularly helpful, but any feedback is welcome! P.S. I am sharing this link across multiple platforms to reach as many lispers as possible. This includes various mailing lists (Lisp Pro, CDR-discuss and -devel for various CL implementations); IRC channels (#commonlisp and implementation-specific ones); the Lisp Discord server; several Telegram groups; and a post on Reddit. If you have any suggestions for additional places to share the link, please let me know. My apologies to those receiving this message multiple times. Best regards, Alexander Fedorov.

1 0

Re: build stack for clasp
by Attila Lendvai 12 Apr '21

12 Apr '21

> Unhappily, I don't have much time to look into this. I see a 2.2kloc > 104KB wscript plus extra shell scripts, and I step back slowly without > taking the threat out of my sight until I'm far enough to run away as > fast as I can. No. Nope. Not unless there's money involved in cleaning > the mess. heh, fair enough! :) i wasn't even expecting you to look. > In general, I recommend writing your script and build system in Lisp. > When there are multiple repositories involved, I currently use Nix to > ensure the build is reproducible though I am considering migrating to > GUIX. If you need high parallelism in a single repo or across repos, I > recommend bazel. i'm also rather happy with Nix(OS). i already started putting together a default.nix file for clasp, and i'll play with it more tomorrow. (it encodes all the necessary external dependencies, and automates setting up an environment with them on any linux where Nix is installed. perfect for CI jobs, too.) > ASDF may or may not be suited to building the software, at which point > UIOP may or may not be suited to parallelize the build on a single > multiprocessor machine. i'm sure parts of UIOP would be useful. i'm not sure i'd get the complexity of ASDF on my shoulders; much of it seems to be due to legacy cruft. > Sorry my comments aren't very helpful. no, it's already helpful, thank you! - attila

1 0

build stack for clasp
by Attila Lendvai 12 Apr '21

12 Apr '21

Fare, (CC'ing the clasp-devel list, also) i would like to ask your bird's eye view perspective on this: what do you think would be a reasonable/practical/feasible build system for clasp if its build were rewritten today? currently it's using waf, a python thingy which works nicely at the initial phase, when things are simple, but it is a major PITA after that. now that there's quicklisp to fetch the dependencies, would it make sense to just write a Common Lisp program as the build script? there's already a python.exe and a waf dependency... a working cl.exe as a dependency is not any worse than that i guess. or do you have any better ideas than a CL program, that is simple but extensible for complex tasks? (e.g. compiling custom programs that scrape through the sources, generating intermediate build artifacts, whole program compilation with extensions on the C++ level (clasp is LLVM and C++)) feel free to be short, and thanks for your time! - attila PGP: 5D5F 45C7 DFCD 0A39

1 0

Nightly Build for Ubuntu
by Gunter Königsmann 06 Oct '19

06 Oct '19

Dear all, I only have 4 Gigabytes of RAM so I thought it would be fun to make launchpad compile a nightly build of clasp fpr Ubuntu I can install without fussing with a docker image. All I tried can be found at https://launchpad.net/clasp-lisp How far I got was: * I perhaps managed to write build instructions for debhelper that create a clasp packages * But during the build waf downloads git repositories. Which isn't possible on the build server as the virtual machine that does the actual build has no internet connection * While the virtual machine is created I have access to local git repos, though => tried to make a mirror of sicl on launchpad that can be cloned into the right directory of the source tree. * ...but the waf script still tries to clone the original git dir and fails, see https://launchpadlibrarian.net/445469670/buildlog.txt.gz Is there any way around this? Kind regards, Gunter.

2 2

New LLVM JIT Features - Views!
by preejackie 02 Apr '19

02 Apr '19

Hi I'm Praveen Velliengiri, student from India. I'm working on developing a Speculative compilation support in LLVM ORC JIT Infrastructure and proposing the same for GSoC19 with LLVM. As LLVM ORC supports compiling in multiple backend threads, it would be effective if we compile the functions speculatively before they are called by the executing function. So when we request JIT to compile a function, JIT will immediately returns the function address for raw executable bits. This will greatly reduce the JIT latencies in modern multi-core machines. And also I'm working on designing a ORC in-place dynamic profiling support, by this JIT will automatically able to identify the hot functions, and compile it in higher optimization level to achieve good performance. I'm proposing this project for GSoC 2019. It would be helpful to know how this new features are effective to clasp, so that I include your comments in "View from Clients" section in my GSoC proposal. Please reply :) -- Have a great day! PreeJackie

1 0

how to fork and record patches to foreign projects
by Attila Lendvai 21 Mar '18

21 Mar '18

aka the mess in clasp-developers. a few thoughts that may be useful: when we fork a repo into clasp-developers, i advice to create a branch in it called 'clasp', or some specific name of a new feature, i.e. *not* the master branch. git checkout -b new-branch if new patches are needed from upstream master, then *rebase* the extra patches to the newly pulled master. don't merge the branches, because that quickly renders git-commit based comparison useless. first make sure you don't have pending changes. if you have, then you can use this to save/restore them: git stash git stash pop then: git checkout master git pull master git checkout my-branch-to-be-rebased git rebase --verbose master if some problem happens, you can either: git rebase --abort or fix the conflict by hand in the working copy, and then: git diff git add whatever-changed.lisp git status # to see that everything has been staged git rebase --continue if you want to drop some patches while rebasing, then do: git rebase -i master and then just delete the relevant lines in the editor that pops up, then save, and quit to continue. this is especially useful when a parallel branch/fork is expected to be open for a longer time. the current cffi and its master branch is a good example of what shouldn't be done. --- IMO, avoiding merge commits in general is a good idea, unless it's really a significant merge that you want to keep recorded in the history, or if you want to GPG sign the merge commit. you can also attempt a fast-forward pull, e.g. when dev was pulled into master: git pull --ff-only . some-other-branch this may fail without changing anything in the repo if it's not possible to pull without a merge. when you accept a PR, then on github you can chose the rebase option on the merge button. then the commits just get copied over into the master branch, as if they have been committed there to begin with. --- random note: the new version of git-fetch-revision.sh in the build-refactor branch supports cloning branches other than master, and even specific tags. hth, -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Chaos should be seen as a teacher that teaches us, through the negative, what not to do.” — Mark Passio, http://youtu.be/atjdCbayxYM?t=46m33s

3 4

building CLASP for MPS
by Basile Starynkevitch 21 Dec '17

21 Dec '17

Hello Chris and all, I would like to build (for experimentation) the MPS branch of CLASP. https://github.com/drmeister/clasp/wiki/Clasp-0.5-Build-Instructions mentions in its last step |./waf update_submodules configure build_cboehm| but I am surprised by the last argument (shouldn't it mention MPS?). Or is Boehm's GC only used (and needed) for the first bootstrap?. (perhaps the wikl page about building Clasp should give instructions for MPS flavor?) Regards -- Basile STARYNKEVITCH == http://starynkevitch.net/Basile opinions are mine only - les opinions sont seulement miennes Bourg La Reine, France

2 2

ASDF 3.1.1 is released
by Robert Goldman 15 Nov '17

15 Nov '17

Here is the announcement. Because this fixes a backwards-compatibility bug, we strongly encourage you to replace 3.3.0 with 3.3.1 in your implementations. Best regards, Robert Today we release ASDF 3.3.1, the first bugfix release for the 3.3.0 release series. Of primary interest in this release are 1. a fix for an incompatibility in the UIOP stamp-comparison functions. The handling of infinity as a bound in these functions changed between 3.2 and 3.3, potentially causing problems in backward compatibility. In order to maintain compatibility, the old behavior was restored to the stamp-comparison functions, and new functions -- TIMEstamp comparison functions -- were added to carry the new behaviors. 2. a fix for upgrade from version 3.2.1 3. fixes for bugs that can occur when the default readtable is manipulated inside a dependency loaded by DEFSYSTEM-DEPENDS-ON. We urge implementations that are currently bundling previous versions of ASDF -- and especially those bundling 3.3.0 -- to upgrade to 3.3.1 at their earliest convenience. Here is the changelog entry for 3.3.1: cl-asdf (2:3.3.167-1) unstable; urgency=low New milestone: * UIOP compatibility fix: Introduced new replacement "timestamp" comparison functions, because of inadvertent change in the API. Functions that are compatible with the old semantics are retained as "stamp" comparison functions, but will eventually be deprecated. * Upgrade fix: Upgrade from 3.2.1 needed repair. * Syntax manipulation: Fix for bugs that could be introduced when the default readtable was manipulated during the loading of a defsystem-depends-on system. * Tests: tests for new capabilities and bugs * Documentation: a number of improvements and clarifications.

1 0

help getting started on Mac
by Jim Newton 18 Apr '16

18 Apr '16

I’m trying to get started with Clasp. I cloned a copy of the git repo. I looked at the README.md file instructions. First it says to try to download a precompiled release from https://github.com/drmeister/clasp/releases But when I look on that web page it says: Please do not use the "source code" downloads below; clone the repository instead, OK, so maybe the README.md is out of date? So I though about trying to compile it myself. The README.md file says to follow an extra step for Mac detailed on the page https://github.com/drmeister/clasp/wiki/Building-Clasp-on-OS-X-requires-usi… But I really don’t understand what that page is telling me to do. Here’s what I read there. Building Clasp on OS X requires using the same version of Clang that Clasp is linked with. I use the llvm/clang version that gets built by externals-clasp. This clang needs to be informed where OS X compiler resources (header files) are located. So the following symbolic link needs to be installed. Let's say the external clang executable is installed at /Users/meister/Development/externals-clasp/build/release/bin/clang. Questions: Am I supposed to understand which version of Clang Clasp is linked with? Especially before I’ve compiled the first time? What is “external clang”? I see that on my system clang is in /usr/bin/clang. Do I need to install another clang? If someone could give me some more help, that’d be great. Kind regards Jim

3 2

Any news?
by Adrian Sampaleanu 20 Nov '15

20 Nov '15

Hi Christian, I keep checking your blog every week for news, but it seems pretty static recently. Anything exciting you can share? -- Adrian

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

clasp-devel