freenode/#clasp - IRC Chatlog
Search
7:03:08
drmeister
I'm looking for it - it isn't in my local repo of ironclad (obviously out of date)
7:04:32
beach
I think if you could characterize what is special about that function, and then get some timing data, that would be a good start for improving compilation times. As opposed to guessing and improving parts that have only a marginal impact on performance.
7:05:42
beach
I am personally guessing (but I don't want my guess to be the basis if an attempt to improve it) that the way lexical compile-time environments are handled could be problematic, especially if your generic dispatch is not terribly efficient.
7:11:01
beach
Since dynamic extent is fishy, I am reluctant to include it in SICL until I know more about it.
7:11:33
beach
SBCL basically trusts the programmer's declaration, which would be unacceptable in SICL, for safety reasons.
7:12:49
drmeister
::notify Bike - One ironclad function (http://paste.lisp.org/display/350808) - takes a huge amount (2439 seconds) - the pass is mark-dynamic-extent (1818 seconds). The next function after that is only 259 seconds.
7:14:04
drmeister
We went on a big 18km hike today to an alpine lake - I'm very sore and tired - I'm off to bed.
11:51:36
Colleen
Bike: drmeister said 4 hours, 38 minutes ago: - One ironclad function (http://paste.lisp.org/display/350808) - takes a huge amount (2439 seconds) - the pass is mark-dynamic-extent (1818 seconds). The next function after that is only 259 seconds.