freenode/clasp - IRC Chatlog

6:48:42 Shinmera !topic :logs https://irclog.tymoon.eu/freenode/clasp

6:48:42 Colleen ** TOPIC Clasp Developer Hangout - Combining CL and C++ for science | <https://github.com/drmeister/clasp> | <https://irclog.tymoon.eu/freenode/clasp> | <https://mailman.common-lisp.net/listinfo/clasp-devel> | Breaking News: <drmeister> I have the righteous sword of inlining to slay the princess and release the beautiful arithmetic dragon

7:21:56 aap_ ** NICK aap

8:59:53 faheem__ Hello everyone.

9:04:31 drmeister Hi faheem__

9:05:55 drmeister minion: memo for stassats: ext:compiled-function-file seems to work for me and M-. M-, jump me where I expect to go. Maybe I fixed it? My latest changes are in "newbuild"

9:05:55 minion Remembered. I'll tell stassats when he/she/it next speaks.

9:06:10 stassats minion: forget my memos

9:06:10 minion OK, I threw it out.

9:07:11 stassats i will start a build

9:07:32 drmeister Oh, you are up.

9:08:57 drmeister I also converted some more dynamic casts to static casts as suggested by beach

9:11:20 drmeister I've rewritten these special operators:

9:11:23 drmeister https://www.irccloud.com/pastebin/cwJ6hQxQ/

9:12:46 drmeister I'm generating these structs...

9:13:05 drmeister https://www.irccloud.com/pastebin/bPgO3fts/

9:13:57 drmeister I have LET/LET* and FUNCTION.

9:14:17 stassats what is dynamic-go-ast and local-go-ast?

9:14:29 drmeister Currently I'm still using activation frames on the heap but in principle I could switch over to stack based frames and closures.

9:14:53 drmeister I'm still a little uncertain of how the environment analysis is to be performed.

9:15:20 drmeister dynamic-go-ast is a GO between functions. local-go-ast is a GO within a function.

9:15:53 drmeister dynamic-go-ast uses exception handling and local-go-ast uses environment cleanup/branch instructions.

9:16:31 stassats i don't see a representation for variables

9:17:11 drmeister variable-get-ast and variable-set-ast - I'm still a little uncertain about those as well.

9:17:22 stassats those are operations, not variables

9:18:13 stassats you need the same variable to map to the same structure

9:18:55 faheem__ Hi drmeister. Still up?

9:19:09 drmeister faheem__: Barely.

9:20:24 drmeister stassats: I'll think on that. They most certainly do otherwise nothing would work. The variable-get-ast looks up the symbol in the environment and returns instructions for retrieving the variable (it's still works like an interpreter). Maybe I can do something more efficient now.

9:20:59 stassats have a special variable, *current-lexical-env*, each time you start a new processing a body of LET/TAGBODY/LET, create a new instance of the environment with the added lexical information

9:21:10 stassats then the body will consult the environment

9:21:45 stassats now you also need a way to mark where the variables are coming from, so that if it's not originating from the same LAMBDA, they can be marked as captured

9:21:46 drmeister Hmm, I've been associating the environment with the AST nodes.

9:22:53 stassats so, another variable *current-lambda* or *current-function*

9:22:58 drmeister The MINCOMP-XXX functions return these AST nodes and they have environments associated with then

9:23:15 drmeister Ok, those I can define.

9:24:06 stassats when you start processing a lamda make it (let* ((new-lambda (make-lambda lambda-list)) (*current-lambda* new-lambda)) (setf (body new-lambda) (process-body ...)))

9:24:07 drmeister I also have CXX-OBJECT and CXX-CLASS defined.

9:24:19 drmeister I specialized PRINT-OBJECT on CXX-OBJECT

9:24:35 stassats and when create variables you do something like (make-variable name value home-lambda)

9:24:57 stassats then when you encounter a variable reference you see whether home-lambda matches *current-lambda*

9:25:34 stassats that's a rough idea of a one way to do that

9:26:06 drmeister Ok, I'll think about it tomorrow - I can barely keep my eyes open now.

9:27:10 stassats or alternatively you can mark each node with the lambda node, then when you read or write a variable you push the node which reads or writes to the list of variable writers/readers

9:27:45 stassats then when you process the resulting tree, you can check whether the variables are always read and written from within the same lambda

9:27:50 stassats if not, allocate closures

9:36:53 stassats but maybe if you're not making a complex IR (since you're going to rely on cleavir), you don't need to collect readers/writers, just mark variables as being closed-over the time you encounter them

10:57:45 beach` ** NICK beach

12:01:23 trig-ger_ ** NICK trig-ger

12:43:11 EdanCoriiin ** NICK EdanCorin

13:21:58 KingNato_ ** NICK KingNato

14:02:19 echo-are` ** NICK echo-area

15:14:34 beach Good afternoon everyone!

15:16:02 clique good afternoon beach