Date: Fri, 11 May 2012 17:26:13 +0800 From: myrice <qqlddg@...il.com> To: john-dev@...ts.openwall.com Subject: Re: OpenCL SWAP64 on 7970 Hi, ALL On Sun, May 6, 2012 at 11:43 PM, jfoug <jfoug@....net> wrote: > If n already is a ulong, then the proper casting would be: > > ((n & ((ulong)0xff00UL)) << 24) > > > Another option may be: > > ((n<<24)&0xff00000000UL) It is very weird that non of these worked. After tested for a long time, I even not sure about the problem. My situation is: while I commented out all the thing inside my opencl kernel only left SWAP64(ctx.H), the SWAPT64 is right. However, when I left some more code in sha512, the problem of SWAP64(ctx.H) occurs as I stated. Please notice that, ctx.H is assigned to an int64 constant in the beginning and untouched in the following code. I cannot understand this weird behavior of my code on 7970. I think I have to move forward and left this problem. Samuele, if you have time, you can pull magnum-jumbo and test xsha512-opencl on other cards. I want to know is this problem only occur on 7970. Thanks! myrice
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.