freenode/#clasp - IRC Chatlog
Search
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
4:19:00
drmeister
I'm not sure what is going on there - I'm improving the backtraces to make it easier to debug
4:31:36
drmeister
Actually, the types should match - there is something going wrong with the equal test
4:32:53
drmeister
It compares the value type to the (llvm-sys:get-contained-type (llvm-sys:get-type destination))
4:34:31
drmeister
So something is wrong with the types in this test: https://github.com/drmeister/clasp/blob/dev/src/llvmo/llvmoExpose.cc#L2908
4:39:16
drmeister
Hmm, maybe it's multithreading and the types are not being declared in the same threads. Where are these defined? (cc-mir:lexical-location-type datum)
4:39:56
drmeister
Maybe you are defining them in one thread - rather than looking them up in the context when you use them.
5:02:08
drmeister
::notify Bike Where do you define the types that you use for the alloca and for the datum?