This is more of a question than an issue since functionally, all the samples will operate correctly, but I noticed that the invocation to SpdResetAtomicCounter will issue an uncached write on all threads for the last remaining thread group. Is this intentional by any chance? Perhaps because the driver somehow realizes that the value being written is uniform and thus can be coalesced? Or would it have been better to restrict the invocation of SpdResetAtomicCounter to the thread with localInvocationIndex == 0?
This is more of a question than an issue since functionally, all the samples will operate correctly, but I noticed that the invocation to
SpdResetAtomicCounterwill issue an uncached write on all threads for the last remaining thread group. Is this intentional by any chance? Perhaps because the driver somehow realizes that the value being written is uniform and thus can be coalesced? Or would it have been better to restrict the invocation ofSpdResetAtomicCounterto the thread withlocalInvocationIndex == 0?