Feb 27 2020
Feb 26 2020
Feb 3 2017
Is there a description how to do that? has the process been started?
Is there an alternative implementation with compatible license?
Why is this necessary? is the explicit mention of "merge ... sublicense and/or sell" the dealbraker?
Feb 2 2017
I repeat here one of the important earlier comment from @tstellarAMD , since it is not in the description and easy to miss:I added two new Intrinsic attributes IntrNoSideEffects and IntrHasSideEffects, which make it possible to specify all the possible memory interaction / side effect combinations. With these properties in place, it should be possible in the future to drop the 'no side effect' portion of the intrinsic memory properties once targets have been updated to use these new properties.
Add some build fixes from awatry.
Also remove tgamma which calls lgamma.
Correctly remove predecessors and clean up some of the loops.
Feb 1 2017
Another possible issue is that SMEM instructions ignore bits of the resource descriptor. So you would need some way to tell the compiler that it wouldn't be ignoring some relevant resource bits by selecting to SMEM.
Would you please describe the purpose of this patch? It's not obvious why it's useful.
Update definition in LangReg.
I haven't looked in too much detail yet. I assume getelementptr doesn't work with these pointers, so it would be good to have a negative test which ensures that GEP use fails.
Jan 31 2017
What if something else has written to the buffer in the same shader? That would make using smem instructions illegal.
How is this different from using amdgcn.buffer.load if D28993 lands (which is not certain)?
More test cases and rebase on top of latest master.
Fix gen_convert.py and add LLVM file headers to all files.
Remove lgamma functions too.
Jan 30 2017
Jan 27 2017
Keep track of visited register class and make sure that equivalent register
classes are both added to the CoverageData.
Jan 24 2017
Rebase on top of master.
Jan 23 2017
Dec 22 2016
Dec 21 2016
Why are all the test changes for local memory read/write, when the code changes behavior for private memory stores?
Address review comments.
Dec 20 2016