1) Did you try to enable the logging flag in order to get in debug mode the BROOK_RT_LOG file, you should have more hints.
2)what about running it for a while (check purpose) in CPU mode ?
Having said so I suspect too a k_map() bug related to the overall numberof input streams as I reported in :
1. I have not enabled the log file, but it runs fine if BRT_RUNTIME=CPU not that that means much since the differences are not documented anywhere.
2. Can someone from AMD confirm whether or not this is indeed a bug?
It still seems like AMD is unconcerned with doing anything with Brook+, maybe they are phasing it out, I don't know. Meanwhile, CAL is simply not practical for writing from scratch unless your kernel(s) is uber-simple. My code uses 6 long/complex kernels, CAL is not an option for me.
AMD, any thoughts?
Tried running a similar kernel on Vista32, the program simply collapses,
Entering into windows debug mode, apparently the incriminated code is at :
22D7417D call std::vector<brook:esc::gpu_technique_desc,std::allocator<brook:esc::gpu_technique_desc> >::~vector<brook:esc::gpu_technique_desc,std::allocator<brook:esc::gpu_technique_desc> > (22D611FEh)
Well, sounds like a bug !!
If you can email a test case that shows this issue to email@example.com then we can have an engineer look at it and see what is going on here.
I'm doing it strait away, you'll get the file mailed in a few minutes.
Thanks for your support.
Could you please have a look too at :
Thanks for the bug report. This has been reported to the correct engineers.
I also see this bug and it keeps me from using the 1.2 SDK. If you come up with any workaround or patch, please let me know ASAP; I do not mind recompiling the runtime or brcc. Thanks a lot