Search
Wednesday, 23rd of September 2020, 15:33:21 UTC
18:31:53
Bike
karlosz: i don't know if clasp will be building with bir this week, but if you build the bir branch of clasp you can compile with bir by binding the hooks
18:46:05
karlosz
so building with the bir branch should just work_
18:47:38
Bike
yeah, i mean, it users hir for the actual build still, it's just set up so you can use bir once it's running
19:08:38
Bike
drmeister: (compile nil '(lambda (x) (declare (core:lambda-name id)) x)) => #<FUNCTION CORE:REPL>. is there some way we can hook up the name properly? i'm not sure where the problem is.
19:51:04
drmeister
Thinking... "Hook up the name properly". Do you mean it should print as #<FUNCTION <pkg>:ID> ?
19:51:30
Bike
it works with compile-file.
19:51:40
Bike
but the function description has the name as CORE:REPL for some reason.
19:51:46
Bike
i don't even know where that name originates from.
19:51:48
drmeister
I don't know why it isn't doing that already - annoying.
19:52:14
drmeister
I have a few ideas where that is originating from..
20:47:05
drmeister
Grrr, even when I put traps looking for the name I can't trap it.
21:32:35
drmeister
I can't find it. It's magic apparently.
21:32:49
drmeister
How the eff does that function get its name?
21:33:21
drmeister
https://www.irccloud.com/pastebin/pwHkVxC0/
21:34:09
drmeister
I get this when I use:
21:34:11
drmeister
https://www.irccloud.com/pastebin/NtqCcoaV/
21:34:28
drmeister
When I add (format t "function-name -> ~s~%" function-name). to irc-create-function-description
21:35:20
drmeister
https://www.irccloud.com/pastebin/429vOTlZ/
21:35:32
drmeister
But the function-description contains REPL
21:35:51
drmeister
Yet - when I add a trap to...
21:35:53
Bike
the fact that there are two function names is kind of interesting
21:36:25
drmeister
https://www.irccloud.com/pastebin/FDu7cnUa/
21:36:53
drmeister
We must have another way to set the function name in the function-description.
21:37:05
drmeister
I seriously should not be allowed near a computer.
21:37:08
Bike
i'm wondering if maybe there are two functions and thus two function descriptions
21:37:10
drmeister
Why do I do this to myself?
21:37:16
Bike
and one of those descriptions is stupid
21:37:31
Bike
oh, i guess the other one could be for the (defparameter ...) form
21:37:46
drmeister
But... (defparameter *f* (compile nil '(lambda (x) (declare (core:lambda-name id)) x)))
21:38:30
drmeister
*f* -> #<FUNCTION CORE:REPL>
21:38:50
drmeister
(core:dump-function-description *f*) --> functionName CDR[146] = REPL
21:39:38
drmeister
Yet in irc-create-function-description it's getting LAMBDA and ID.
21:40:24
drmeister
When I do the next runtime rearrangment - adding multiple entry points and GC code - I want to straighten this stuff out.
21:40:32
drmeister
So there is only one way that function names get defined.
21:41:20
drmeister
Hang on - I'm doing this in cclasp.
21:41:44
drmeister
If it's different in bclasp then maybe I can find it in the cleavir interface.
21:42:28
Bike
i haven't tried it in bclasp.
21:42:59
drmeister
Well, this much is the same...
21:43:00
drmeister
https://www.irccloud.com/pastebin/casGaysM/
21:43:16
drmeister
Do you know where the function printer is?
21:43:28
drmeister
It doesn't appear to be the __repr__ method in functor.cc
21:43:29
Bike
yeah, it's in write_ugly.cc.
21:43:36
Bike
it juse uses functionName().
21:43:52
drmeister
Ok, so it's a question of how does it get set.
21:44:08
Bike
what's also weird is it looks like the llvm name of the function is set correctly
3:16:25
beach
Good morning everyone!
Thursday, 24th of September 2020, 3:33:21 UTC