freenode/#sicl - IRC Chatlog
Search
9:11:37
no-defun-allowed
With regards to the statement "The access tag consists of the 4 most signicant bits of a 64-bit pointer" in page 19 of the CLOSOS specification, I was informed that the most significant bits of the pointer have to be the same as the most significant bit that is used in addressing.
9:17:23
no-defun-allowed
shka__: This is about access control bits in CLOSOS, which are not tag bits.
9:19:45
no-defun-allowed
But I got into another terrible discussion after making a quite shocking joke about using a difficult-to-install Linux distribution, and that is something I need to learn not to do, or I need to learn to change the topic quickly.
9:22:25
no-defun-allowed
It wasn't really a joke, but I responded to "installing arch is actually a good learning experience and isn't that hard so if you're interested in like learning more about linux + getting better customization I'd go that route" with "You won't learn anything new from using a difficult to maintain distribution, other how bad the design of GNU/Linux can get."
9:23:41
no-defun-allowed
I guess it was funny to me because the former was my mentality four years ago, and it didn't work out at all.
9:25:46
beach
People who have spent a large part of their lives investing in some technology often take it personally when someone tries to point out that that particular technology might not be optimal.
9:26:53
no-defun-allowed
(And in my opinion, what you learn instead is how to get from the live disk to a new bootable system in as little time as possible, possibly reinforced through several attempts at getting the damn thing to boot, which is much less than what was promised.)
16:55:14
beach
So, yesterday (or the day before, I forget) I decided to visualize the result of HIR-to-MIR for the first time, using the IR visualizer, of course. It turns out that it was very wrong. Mainly due to some :AROUND methods on SHARED-INITIALIZE that I should have seen would not work the way I planned.
16:55:54
beach
So I spent some time fixing things up, and improving the visualizer so that I can see more stuff, including raw integers.
16:57:49
beach
There are a few quirks left, but I think I am close to done with HIR-to-MIR. I need to convince the visualizer to show me nested functions which are no longer represented by ENCLOSE-INSTRUCTIONs in MIR, so that I can view the guts of the code, as opposed to just the code that gets executed at load (or "tie") time.
16:59:40
beach
Once I am done with HIR-to-MIR, I'll work some more on MIR-to-LIR. Recall that MIR is where address calculations become explicit, and LIR is where registers are introduced.
17:00:53
beach
So in MIR, AREF and STANDARD-INSTANCE-ACESS and such have been replaced by memory references. And tags are eliminated before memory is addressed.
17:27:45
beach
The pink inputs are fixnums, and should be replaced by yellow ones which are immediate machine integers.
17:29:02
beach
The last yellow 0 represents an entry point, and the FUNCALL calls ENCLOSE to create a closure. that it then returns.
17:29:44
beach
The yellow 0 is an immediate integer, but it's a subclass that contains the ENTER-INSTRUCTION for the entry point.
17:30:29
beach
I need to teach the visualizer to show me the contents of an entry point of such an immediate integer.
17:31:25
beach
Everything that precedes is basically filling up the static environment of the closure it creates with constants and global functions.
17:45:32
beach
I'm off to have dinner with my (admittedly small) family, and then spend some time with her.
18:03:18
alandipert
very cool, thanks for sharing. it motivates me to keep visualization in mind as i proceed with my increasingly complicated thing
18:03:39
alandipert
when you have a chance i'd be curious to see the code that corresponds to the picture, if you have it handy