llvm-project
ulisp
llvm-project | ulisp | |
---|---|---|
10 | 33 | |
217 | 361 | |
0.0% | - | |
0.0 | 2.6 | |
13 days ago | about 1 year ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
llvm-project
-
platformio integration with neovim?
I forgot to say that I use this llvm build. Just download the release and point the clangd server to it.
-
LLVM 16.0.0 Release
Xtensa support (esp32). Will be interesting how this will be for Rust and Zig support for esp32
https://github.com/llvm/llvm-project/tree/main/llvm/lib/Targ...
https://www.phoronix.com/news/LLVM-Xtensa-Backend
https://github.com/espressif/llvm-project/issues/4#issuecomm...
https://github.com/ziglang/zig/issues/5467#issuecomment-1465...
-
How do I program an ESP32 S3 in Rust using podman from WSL?
Hopefully, in the future the installation will be simpler, as we are trying to upstream our LLVM changes (first 10 patches are already accepted!), and once we manage to upstream LLVM changes we will proceed with upstreaming our Rust fork changes.
-
Using Vim as an editor for ESP-IDF
The main discussion can be led back to this GitHub issue and this comment; fortunately, we don't need to build espressif's llvm fork anymore as they supply the clangd (this is the language server we need) and you can find the zip here. I'll briefly list down the steps required to set up vim with clangd to take advantage of clangd's features (auto-completion, linting, code refactoring ...)
-
The more I use other MCUs the more I like the ESP32
In my case, it's pretty annoying that the Xtensa platform doesn't have official LLVM support. It's in progress but going very slowly.
-
Have you ever started a project in Rust but switched to a different language? If so, why?
The link to the espressive issue trackers: https://github.com/espressif/llvm-project/issues/4
-
Are there situations where it's better to use C++?
Xtensa. They've got a fork of LLVM that supports it that they're working toward getting upstreamed. The community has a fork of rustc that uses it (and a quickstart crate) while we wait for it to get upstreamed.
-
Rust and GCC, two different ways
https://github.com/espressif/llvm-project/issues/4 is a good example why updating llvm isn't easy and takes a lot of time.
- Tomu – An ARM microprocessor which fits in your USB port
-
uLisp
Just to clarify - Gambit, Chicken, and Carp all compile to portable C.
I hadn't realized LLVM mainline doesn't support Xtensa. I'm surprised.
D does support Xtensa via LDC (https://forum.dlang.org/thread/[email protected]...). It looks like GDC also nearly supports it, requiring only a minor patch at present.
A functioning LLVM backend does exist (https://github.com/espressif/llvm-project/issues/4) and might be making very slow progress towards being merged. A quick search shows that it works for Rust. I suspect (but don't know) that it might work for Terra as well.
There's also the LLVM C backend (https://github.com/JuliaComputingOSS/llvm-cbe) but I've no idea how efficient such an approach is when applied to real world embedded tasks.
ulisp
- How to Write a (Lisp) Interpreter (In Python)
- Show HN: I Made a Lisp
-
Lisp Badge LE
I love his projects too. He's also the creator of uLisp.
http://www.ulisp.com/
-
Lisp in Space
Not CL, but there is ulisp (http://www.ulisp.com/) for microcontrollers, supposed to be really tiny, and there is Carp (https://github.com/carp-lang/Carp) which is without a GC so seems suitable for real-time stuff.
- uLisp: Lisp for Microcontrollers
-
fe: A tiny, embeddable language implemented in ANSI C
There's also ulisp (for Arduino projects etc.): http://www.ulisp.com/
This is larger, because there are functions for accessing peripherals, and the core is more standard lispy with 'caadr' et.al., and it has a compacting GC, so images can be saved as a compact blob.
- ¿Any interpreted lenguage working in low memory microcontrollers?
-
Anyone tried to run ECL on a Pi Pico?
You might consider uLisp, it's very Common Lispy for the memory constraints given (sans macros and splicing quote). And you can still connect to it and save an image. I've tried it and it works well enough. Here is the homepage.
- Scamp – a self-contained Forth computer
-
What do you think of Forth?
Agreed - the interactivity is good. Lisp is close (have you seen http://www.ulisp.com/ - I can't believe they got into into that small a target!). Python is ok, but for some reason I don't use the REPL in the same way I do in Forth - I think calling functions is just harder somehow. Mostly is exploring valves from the Python REPL.
What are some alternatives?
llvm-cbe - resurrected LLVM "C Backend", with improvements
ecl
Lua-RTOS-ESP32 - Lua RTOS for ESP32
terra - Terra is a low-level system programming language that is embedded in and meta-programmed by the Lua programming language.
ferret - Ferret is a free software lisp implementation for real time embedded control systems.
lispBM - An interpreter for a concurrent lisp-like language with message-passing and pattern-matching implemented in C.
nim-esp8266-sdk - Nim wrapper for the ESP8266 NON-OS SDK
tinyscheme - TinyScheme is easy to learn and modify. It is structured like a meta-interpreter, only it is written in C.
ulisp-builder - Builds a version of uLisp for a particular platform from a common repository of source files
quickjs-esp32 - QuickJS port for ESP32