1) No need to re-run on Linux. Linux dev confirmed that he can compile under Linux now (after driver reinstall and Linux update). So it was some glitch and he can't reproduce it now. Hence no need to waste more time on this.
2) Driver crash on execution come most probably from too lengthly kernel.
As I reported in another thread there are 12 registers allocated per kernel workitem under Cat 12.8 while only 5 under Cat 13.1. So, I think register spills are inevitable that degrades performance under red line of driver restart.
Driver crash on compilation stage is quite another issue but again, I'm not quite sure is it stable reproducible (you saw this issue once but it gone after one more driver reinstall).
Also, app build with different kernels that uses more local memory doesn't suffer from too long kernel execution time so we can just go with that app build for now. Not show-stopper issue.
3) But issue with Catalyst 12.10 is reproducible (unfortunately) and plagues both kinds of app (not all data patterns but in general we can't restrict app from reciving different kind of data patterns as input). Loks like it was fixed in Cat 13.1 though.
Cause hotfix for Cat 12.10 in the presence of 13.1 is highly unlikely I think there is currently no more issues to solve with your help. Thanks a lot for participating! I will create new thread in case latest Catalysts will cause some headaches to keep issue easier to follow. Kernel performance degradation under Cat 13.1 is worth to look into though. So I attach ISA's under different Catalysts (12.8 and 13.1). There is another thread about another (not mine) app that sees same issue of lowering registers usage under 13.1 so maybe worth to look for Catalyst compiler devs.
