freenode/#sicl - IRC Chatlog
Search
18:25:12
heisig
I just gave up on finding a short, memorable name that includes CL and is not yet taken.
18:26:48
heisig
ck_: I am tempted to relax 'must include CL' to 'must be a pun on Lisp'. Which would open up 's-expressionists'.
18:29:05
heisig
Thanks! I also found a lot of names that are much worse, e.g., 'indefinite-extenders'.
18:32:28
ck_
also, if we want to use bottom shelf to inspire some creativity, I can offer "McCarthyists"
18:34:43
heisig
I was thinking about that one, too. But I'd like the name to have a certain progressive and artistic touch.
18:39:36
ck_
If all else fails, I bet we can write to rpg, he'll come up with something! Using the power of his MFA
5:44:41
beach
The goal for today is to make progress on turning the top-level function in HIR to one that can ultimately be compiled to native code.
5:44:48
beach
For that to be possible, I need to move the constants out of it and put them in the static environment of that function.
5:44:54
beach
I plan to do that bey defining a subclass of the TOP-LEVEL-ENTER-INSTRUCTION that has an additional slot for hoisted constants.
5:45:01
beach
The code of the top-level function will refer to the static environment for constants, and the non-native code for enclosing the top-level function will create the closer with a static environment containing those constants.
5:46:45
beach
Oh, and recall that the top-level function in HIR is the one that gets executed in order to "tie" the code to a particular environment.
5:47:25
beach
So I want the top-level function in HIR to be structured in a way that it can be turned into MIR, but it should still be possible to turn it into host Common Lisp for execution in the host during bootstrapping.
5:53:50
ck_
beach: this channel seems like an awesome set of labnotes for you. have you ever used it for that purpose, I mean, looked up something from say last year?
5:53:54
beach
It would be possible to leave the HIR code as it is, for the purpose of translating it to Common Lisp for execution in the host, and only restructure it as described above in order to turn it into HIR.
5:55:08
beach
Also, sometimes people catch me saying stupid things, which is great. I can then rethink my plans.
5:55:11
ck_
I never tried writing notes as if explaining them to a channel full of people. Worth a try definitely, thanks for the demonstration :)
5:56:01
beach
I can't use pens very much anymore. The muscles have not been trained to do more than a shopping list.
5:58:30
ck_
I meant that, if I were to try it, writing as if there was an audience doesn't translate so well if feedback is important.
6:01:05
beach
I really don't have any preference about the name, as long as it is unique and that it suggests the purpose.
6:08:48
beach
So, continuing, like I said, I could apply the transformation described above just to HIR code meant to be translated to MIR and ultimately to native code. But recall that I decided that MIR code is going to be very hard, or impossible, to test before it is turned into native code and executed in a native SICL environment.
6:09:36
beach
At that point, I will lose all my debugging tools, and I will be stuck with looking at disassembly listings, or (worse), machine code in hex format.
6:10:22
beach
So, my plan for avoiding that is to apply as many transformations as possible before the HIR code is turned into Common Lisp code for execution in the host.
6:11:34
beach
And turning the top-level HIR function into something that can ultimately be turned into native code, while preserving the possibility of turning it into Common Lisp for execution in the host, is part of this strategy.
6:13:03
beach
But right now I have more urgent things to think about, namely to go run some errands.