freenode/lisp - IRC Chatlog
Search
2:01:33
brownxoat
hey, I am an idiot trying to get abcl working on windows. can anyone help? I am getting "spawning child process: invalid argument" with this setq
2:01:54
brownxoat
(setq inferior-lisp-program (concat "c:/Program\ Files/Java/jdk-16.0.1/bin/java.exe" " -jar " "c:/Program\ Files/abcl/abcl.jar"))
2:10:17
|3b|
brownxoat: might try (concat "\"c:/Program Files/Java/jdk-16.0.1/bin/java.exe\"" " -jar " "\"c:/Program Files/abcl/abcl.jar\"") or using slime-lisp-implementations instead of inferior-lisp-program
2:17:25
brownxoat
(setq inferior-lisp-program (concat "\"c:/Program\ Files/Java/jdk-16.0.1/bin/java.exe\"" " -jar " "\"c:/Program\ Files/abcl/abcl.jar\""))
2:18:02
brownxoat
Searching for program: no such file or directory, "c:/ProgramFiles/Java/jdk-16.0.1/java.exe"
2:20:27
brownxoat
|3b|: hmm, without \ I get: Searching for program: No such file or directory, "c:/Program
2:22:08
|3b|
ok, maybe that doesn't work then, try slime-lisp-implementations which takes program name and args as separate strings
2:23:40
|3b|
(setq slime-lisp-implementations '((abcl ("c:/Program Files..." "-jar" "c:/Program Files/...")))) (setq slime-default-lisp 'abcl)
2:27:12
|3b|
not sure if there is general agreement about moving yet (or to what channel if so), though looks like some people have moved
2:27:13
brownxoat
|3b|: the last I heard is that sbcl is missing threads or something on windows, which made me stay away from it. I just heard people backtalking sbcl on windows on the internet for the last few years, so I didn't even consider it.
2:27:57
|3b|
it has threads, and i've been using sbcl/windows as my main dev setup for years with no particular problems
2:29:54
|3b|
(the test suite has some things that break on windows, but probably mostly not things you'd do too often in real code, like constantly running GC in one thread while constantly recompiling files in another, or whatever)
2:29:56
brownxoat
I don't get what happened to ccl though :( https://github.com/Clozure/ccl/issues/311
7:09:51
jnewton
I'm reading something which directly contradicts a fundamental principle of how RISC works. Maybe my understanding has been wrong all this time.
7:13:43
jnewton
My question is if I load (write) data into a register, and in the next instruction I try to read from that register. will I (1) read the old value, or (2) will the processor automatically stall waiting for the data to be ready? I though (1) was the case and that that was considered a feature.
7:13:51
jdz
jnewton: There was an article how Apple's new CPU can have sane instruction stream decoding and speculative execution (because of constant instruction sizes), whereas x86 is screwed because it has to process too many false positives since it has to try instructions at every byte position.
7:15:35
jdz
jnewton: Stalls are usually associated with writes/reads to memory. And even then CPUs speculate.
7:17:13
jdz
jnewton: AMD CPUs do even more: https://www.amd.com/system/files/documents/security-analysis-predictive-store-forwarding.pdf
7:17:55
|3b|
ACTION thought it was generally a 'feature' of RISC to /not/ automatically do things for you
7:19:58
jnewton
|3b|: that was what I thought as well. i.e., you were allowed to write, and still read the old value for one cycle.
7:21:08
jnewton
Sorry I know this is not a lispy conversation. just thought there might be someone here that could clear up my confusion
7:21:51
beach
jnewton: #lisp may be about to move to #commonlisp at libera.chat because of a "hostile takeover" of freenode.
7:25:52
jdz
jnewton: I think this is the article I had in mind: https://debugger.medium.com/why-is-apples-m1-chip-so-fast-3262b158cba2
7:32:03
|3b|
not sure it is even guaranteed to show you the old value on old mips (or anything else with load delay slot), might depend on cache hit, or might stall automatically and delay slot just gives you a chance to do something during the stall
7:47:48
White_Flame
jnewton: "RISC" was a concrete architecture, with a bunch of interconnected tradeoffs. Talking about "RISC style" is as contentious as "What is a Lisp?"