Search
Tuesday, 6th of November 2018, 15:20:57 UTC
17:28:00
drmeister
Hmmm . (core:function-name #'print-object) -> LAMBDA
17:28:11
drmeister
(clos:generic-function-name #'print-object) -> PRINT-OBJECT
17:29:05
Bike
yeah the latter uses the actual slot
17:29:11
Bike
core:function-name checks whatever C++ thingie
17:31:57
drmeister
Did I put LAMBDA into the function-description?
17:32:16
drmeister
What C++ thingie? - I'm wracking my brains trying to figure out where I put this?
17:32:34
Bike
um, the like... function_O
17:32:42
Bike
probably the function description, yeah.
17:37:01
drmeister
I need a freakin' 'where' function to help me find things like M-. without starting up slime.
17:42:56
drmeister
The FuncallableInstance_O::functionName() method returns GFUN_NAME - which isn't LAMBDA
17:43:07
drmeister
Ah - I didn't declare functionName() to be virtual.
17:43:19
drmeister
So FuncallableInstance_O::functionName isn't being invoked.
17:43:33
drmeister
Still, the FunctionDescription shouldn't contain LAMBDA
17:52:05
drmeister
Where do generic functions get their name set?
17:54:32
Bike
i think their name in the function description is just the default
17:55:19
drmeister
It is - I'd like to update it when the name of the generic function is set.
17:56:21
drmeister
Would you add an :after method on the accessor?
17:57:16
Bike
that wouldn't catch initialization or anything
17:57:20
Bike
i guess shared-initialize maybe
17:57:29
Bike
the accessor isn't actually an accessor, it just reads, iirc
17:57:33
specbot
http://metamodular.com/CLOS-MOP/generic-function-name.html
17:57:47
Bike
oh, nope, there's a writer too
18:22:49
Bike
ok keyword parsing phi edition is now working at least well enough to get through aclasp
18:23:25
Bike
on the other hand the actual GENERATED code is smaller now
18:23:54
Bike
that's probably most of it. those invoke instructions get messy
19:41:06
drmeister
It appears that I have a case where the register-save-area is being optimized away.
19:46:05
drmeister
Ho boy - I found an llvm-dev discussion about preventing llvm from optimizing out variables. http://lists.llvm.org/pipermail/llvm-dev/2016-July/102322.html
19:46:28
drmeister
They were discussing it in 2016 - so it is a recent issue.
2:38:06
drmeister
I fixed the stackmaps issue - build time dropped to 27 min on my laptop.
2:39:34
drmeister
slime and sldb work now
2:40:02
drmeister
The backtraces look good - except there are an extra pair of parentheses around the specializers for methods.
2:40:34
drmeister
(defmethod bar (x y) (error "In bar"))
2:41:12
drmeister
https://www.irccloud.com/pastebin/DBddJ9lH/
2:55:39
drmeister
I pushed the changes to dev
2:58:35
drmeister
Once you get the temporaries out I'll be interested to see the impact on the amount of code.
2:59:01
Bike
i think ill probably have fixed up the arguments code by tomorrow
2:59:14
Bike
i already finished the keyword parsing with phi
Wednesday, 7th of November 2018, 3:20:57 UTC