Viewing profile — atgreen

VISA open sourced an expense-to-run harness they developed under glasswing, and I used that as the basis of a skill that I've found to be pretty effective with Claude Code: https:/…

TBH, the complexity of this step grew over time, and the overhead snuck up on us. The prep step does useful work (eg. determine stack space requirements). It's just that we don't h…

Yes, that's part of what was done here. So, create a plan, and then for some subset of plans, create AOT-compiled templates. The analogies are: a) original implementation is like i…

Here's another option.. I created an optimizing eBPF compiler in Common Lisp for a lisp-ish DSL. It's nice because you can compile and load your eBPF code all in-process in lisp (e…

No, they are different. I just bundled them together for convenience in this POC. The only real thing in common is that they both use eBPF.

Have a look at https://github.com/atgreen/rhel-block-copyfail

Don't disagree, but there are eBPF mitigations that work as alternatives to unloading kernel modules.

I created something similar earlier today: https://github.com/atgreen/block-copyfail

This is not my experience. I've been experimenting with something very similar to vera. However my language transpiles into multiple languages (Java, Typescript, Common Lisp, Rust,…

I enjoyed reading this. Thank you for sharing. I learned Common Lisp years ago while working in the AI lab at the University of Toronto, and parts of this article resonated strongl…

Thank you!

The whistler code you inline with your common lisp is an s-expression based DSL. So you can use common lisp macros, but those macros are generating something that will look familia…

Whistler compiles s-expressions to eBPF bytecode and emits ELF object files (no clang/LLVM). It includes an SSA-based optimizer that matches optimized clang code. You can even use …

They are much better these days.

256k is just's just a placeholder for now. The default will get reduced as we get more experience with the draft implementation. The proposal isn't complete yet.

I haven't really looked into it, but I'm hopeful it can be made to work.

No. I have yet to propose the patches formally. The SBCL maintainers are reviewing the high-level proposal (on my blog) first. You can try the implementation, however. There's a po…

This very website that you are using right now, Hacker News, runs on sbcl.

I'm the author. https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

I set out to create a better text repl experience for Common Lisp couple of months ago, but was inspired by the pharo interface and built something much larger: https://atgreen.git…

It's like Dr Ian Malcolm says.. "Your developers were so preoccupied with whether or not they could, they didn't stop to think if they should" - Jurrasic Park (almost)

Here's something I wrote about this work: https://atgreen.github.io/repl-yell/posts/cl-kawa/

If you are interested in this, you might also be interested to learn that I also got clojure running on SBCL via OpenLDK. See https://github.com/atgreen/cl-clojure . Regarding LLM-…

I managed to get a clojure REPL running on Common Lisp (SBCL) via OpenLDK, my Java JIT compiler and runtime on Common Lisp. This blog post gives an overview on how I manipulated CL…