3 ms·
Funny enough I was talking with someone who wanted to make a lisp run on a very small ARM SoC and we discovered that the 7090 Lisp 1.5 was developed on likely h
by aidenn0 4y ago
Funny enough I was talking with someone who wanted to make a lisp run on a very small ARM SoC and we discovered that the 7090 Lisp 1.5 was developed on likely had more core+drum than the SoC had ram.
- pjmlp 4y agoNot even uLisp? That looks like a PIC like CPU to me.
- deleted 4y ago[deleted]
- aidenn0 4y agoThis might have been before uLisp (definitely prior to my knowledge of uLisp), and they wanted to write the interpreter for it themselves. IIRC it had 16k of RAM, so it definitely could have run uLisp. [edit] I should also point out that just storing the names of all of the symbols in the common lisp specification exceeds the RAM requirements of uLisp. Obviously builtins can go in ROM, but it gives you an idea of the sizes involved.
- pjmlp 4y agoI see, thanks for the overview.
- exdsq 4y agouLisp was too large for a small flight computer I made for a hobbyist rocket - I wanted to use it but had such little RAM I had to go down to C. I think I could have ran lisp-to-c to generate from uLisp which I’ll try on my next project.
- pjmlp 4y agoIn such contexts it is more like an Assembly with a C like macro processor than proper ANSI C anyway, and if you go the code generation route, then you would be better off using the DSL capabilites from Lisp to generate Assembly directly.
- deleted 4y ago[deleted]
- bsder 4y agoPeople really underestimate how much RAM a Lisp/Scheme needs. Building lists out of pairs and then using them as your intermediate format creates a lot of garbage.
- kazinator 4y agoThe RAM usage is tied to the size of the reachable set, plus some slack filled with garbage that depends on how you tune the garbage collection thresholds. By today's standards, the RAM usage isn't necessarily huge. Here is the TXR Lisp compiler recompiling stdlib/compiler.tl -> stdlib/compiler.tlo, as seen in top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11488 kaz 20 0 17800 14804 2964 R 98.1 0.7 0:07.07 txr ^^^^^ ^^^^^ On the order of a bash session. It's a lot of RAM by 1982 standards at the institution level, and even 1992 standards at the consumer level, but today it means nothing. You can easily see a Bash process a footprint on that order. It could be reduced by tuning the garbage collector. One way to do that is to build for less memory use (useful for embedded). Here it is with txr rebuilt using #define CONFIG_SMALL_MEM 1 in config.h: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 12838 kaz 20 0 11964 9768 3140 R 99.0 0.5 0:10.39 txr Bash footprints for comparison: $ ps aux | head -1 ; ps aux | grep bash USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND kaz 1093 0.0 0.1 9288 2132 pts/2 Ss+ May15 0:01 -bash kaz 2833 0.0 0.0 8904 1992 pts/0 Ss May15 0:00 -bash kaz 3509 0.0 0.2 10532 4988 pts/1 Ss+ May15 0:28 -bash kaz 7898 0.0 0.1 8968 2212 pts/3 Ss+ May20 0:00 -bash Lists are used for everything: the compiler produces a list-based assembly code which is used from then through assembly. There is an optimizer which divides it into basic blocks, which are objects put into a graph, but the instructions still being lists. The peephole pattern matching is done on lists. The compiler does not bother using destructive append (nconc) for stitching together fragments of code; just straight garbage-generating appends. Same with most of the other rewriting that happens later. In a computer in 1960, your compiler would be capped to the physical memory available. That would be the RAM use. The garbage collector would have to be called whenever the memory is exhausted, or else the show would stop. A successful compilation would demonstrate that the compiler needed no more memory than what the machine has. The closer its actual usage would be to the available memory, the longer it would take, due to the frequent garbage collections required to stay afloat. I'd say that given people's expectations today, shaped by experiences with everyday software, they likely greatly overestimate how much RAM you need for Lisp compiling.