freenode/#clasp - IRC Chatlog
Search
20:27:01
Bike
drmeister: i've just been glancing through the scraper. it seems to me like the easiest way to incorporate the static analyzer stuff would just be to make a sif file out of it and then use the normal machinery? i'm not clear on what the numbers in your example are, though
4:05:59
drmeister
::notify Bike That's an interesting idea - we could generate a sif file directly - we may need to add a bit more to the sif parser to bring all the info in. I'll put a little writeup together and post it for you.
5:01:00
drmeister
::notify bike I took your suggestion of generating a sif file and ran with it. The static analyzer now generates a sif file that has new fields that we need to parse - but it looks just like a sif file. https://gist.github.com/drmeister/b39ea552c7cb235988041118d16d8274
5:03:29
drmeister
::notify bike The tags are new - their names followed a tortuous path through multiple generations of the static analyzer. I may have to explain what some of them mean. But from these sif files we should be able to recreate everything in clasp_gc_cando.cc. We may need to add a few more tags to some of the entries. The way these sif files are now you have to keep track of some state from one entry to the next.
5:33:04
drmeister
::notify Bike I modified the static analyzer to generate a sif file and I pushed the change to github. You can test it with ./waf analyze_test - that will write a build/clasp_gc_test.sif file for analyzing a single file that you hard code into the wscript file analyze_test Python function.
5:34:19
drmeister
Or you can run ./waf clean_impsprep build_impsprep analyze_clasp and it will analyze whatever clasp or cando you are currently working with. It takes 30-60 min on the mac.