freenode/#clasp - IRC Chatlog
Search
16:53:21
drmeister
beach: Clasp also has a header/rack implementation for CLOS objects. Although there are a few more things in the header to mimic ECL-style objects.
17:53:20
Serenitty[m]
Otherwise, the target triple error messages make it practically unusable. It's hard to see the actual output.
18:01:04
Serenitty[m]
Huh. The issue is that it still lags whenever all a slew of those error messages comes up — they're just invisible.
18:03:16
Serenitty[m]
Oh, so it normally takes a minute to compile whenever you define a function in the REPL?
21:25:37
drmeister
I've converted the fastgf over from using a generic function lock to using compare-and-swap on all updates to the call-history and the specializer-profile.
21:31:16
drmeister
Bike: I learned a new trick that helps immensely with debugging in lldb. C++ functions can be defined with __attribute__((optnone)).
21:32:00
drmeister
I'm starting to use that for C++ error functions so that I can get more info on the error.
22:00:38
drmeister
Does find-class need to be fast? What if I implemented it using an alist - would that be a terrible idea?
22:13:51
drmeister
Unless the object fits in a pointer - from what I read it's no better than a lock.
22:14:23
drmeister
I'm not completely certain about that - but it looks like a bad idea to make a large data structure std::atomic - I'm not even sure what it means to do so.
22:15:29
drmeister
Now, that being said - clasp uses a ribcage hash tables (vector of alists) - it may be possible to make that lockless.
22:18:00
drmeister
Implementing fastgf with CAS instructions has opened my eyes to another way to do multi-threaded programming.
22:28:35
drmeister
Well - actually - it may be that slow - but still -what are you trying to compile?
0:57:27
drmeister
Serenitty[m]: I see what you are talking about wrt the target triple. I'm trying something new - to read the target triple out of an llvm-ir file built by clasp.
1:00:31
drmeister
On OS X it doesn't complain as loudly as it does on Linux - so I didn't notice it.
1:44:18
drmeister
I could never get the target triple that I got from llvm to agree with the ones that clang was generating.
1:46:22
drmeister
Also, even with all the warning that were being generated - 20 min have been shaved off the build time.
3:15:16
drmeister
Well, it's not faster - the next build wasn't faster the next time. I'm still rearranging things.
3:23:09
drmeister
Bike: I'm getting this error occasionally - did we see this recently? !!! Mismatch in irc-store between val type #<TYPE float> and destination type #<TYPE float>
3:37:03
drmeister
When I compile-file the static analyzer. I'm getting slime to work with the new backtraces to track things down more easily.
3:46:44
drmeister
I'm going for a minimalist look after the cluttered backtraces we've been dealing with for years.
4:00:35
Bicyclidine
https://github.com/drmeister/clasp/blob/dev/src/lisp/kernel/cleavir/translate.lisp#L38 the alloca, https://github.com/drmeister/clasp/blob/dev/src/lisp/kernel/cleavir/translate.lisp#L817-L819 the store