the tool that I’m trying to reverse engineering doesn’t create any cache in .nv directory, checked with strace. He also forks a lot of “watchdog” threads to break the program when there’s any potential reverse engineering behavior. Apparently, all sass code (both compiled kernels or JIT kernels) will be pushed up to GPU mem (maybe it’s even in RAM), with a little tweak we can get them all.
Anyway, running the tool on sm_75 with the latest driver produces much nicer sass code and so now I can understand it.
Thanks for all the help!
side note: nvdisasm still cannot disasm sm_80 and sm_86.