cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

diapolo
Adept I

status of bitalign and rotate

It seems like amd_bitalign(x, x, (uint)(32 - y)) and rotate(x, (uint)y) currently generate the same code (checked vor Tahiti and Cypress). Is this true for future releases, too, so that I can safely remove amd_bitalign() calls from a kernel. It was only used as a replacement for rotate() in my context.

Thanks,

Dia

0 Likes
1 Solution

Dia,

It is safe to remove amd_bitalign in place of rotate as we now optimize the rotate pattern into bitalign.

View solution in original post

0 Likes
3 Replies

Dia,

It is safe to remove amd_bitalign in place of rotate as we now optimize the rotate pattern into bitalign.

0 Likes

Thanks for that info. By the way, there are still no OpenCL changelog infos in the Catalyst release notes, what's up with that? It was promised quite a few weeks ago.

Dia

Having OpenCL release notes in the monthly Catalyst updates is critically important! We all know that this is an overhead, but updating to a new driver release should not be "plug & pray" exercise for the users/devs

0 Likes