3% faster mining with phoenix+phatk for everyone

[bunnybare]

5770 from ~200 to ~210

Same with me!

Edited BitcoinMiner.cl on poclbm.

[1713488093]

1713488093

[manifold]

works perfectly. Many thanks!!!

[klaaster]

 Very nice hack, gives me 2% to 3% more on HD5850/30.

Great find!  

[forexmasterja]

This works great !!! got an extra 100 MH with all my cards combined. I'm very grateful for this but this is definitely gonna push the difficulty up when this gets more public.

Worth a donation definitely!

6870 295mh => 312mh
5850 350mh => 362mh
6870 411mh => 426mh

Again great find.

[syb3ria]

It's good to know that helps fellow miners, yet i get 16-20 mh\s more with that. http://forum.bitcoin.org/index.php?topic=19051.0. All that is going on Powercolor 5770 @ 990/171 with -f 1 and -f 20 on win 7 x64. Anyway keep up the good work. We all need optimisations

[heroBitcoin]

cool, will try these method

[bitless]

Thanks for your code. It's nice to see people get rewarded for their efforts (though it doesn't always happen). Well, I've tried it on my own miner (minerd) and have some very strange findings.

https://forum.bitcoin.org/index.php?topic=21275.0

First of all, minerd supports up to 4 vectors, and when I add this change to my kernel, it actually _slows down_ the 4 vector version. But when I override it to set 2 vectors, it speeds it up. However, once it's sped up, I then get runs of rejected shares. I tried it multiple times with and without and it does appear to be just this change that causes it, so I'm not sure what's going on.

I honestly do not know what's up with that, I saw ATI asm yesterday for the first time and can't tell you exactly what's wrong yet. All I know is that the truth tables match for the Ma() function with and without my modifications. Yet, here's a couple of ideas -
1 glancing through the doc, radeons are VLIW5 = 4+1, with 4 'normal' pipelines and one transcendental pipe, which can do a restricted set of instructions. I don't know where BFI_INT gets executed, but if it is only in the trans. pipe, then doing too many BFI's can hurt the performance by making that pipe a bottleneck. Check the docs and let us know, if you don't mind.
2 if (z^x) isn't already used in other places in your code, then it may be pushing up the register usage and you're running less threads in parallel. Again, I don't know much about ATI, but it would be the first thing I'd check if we were on nVidia/CUDA.
3 something else altogether...

Not sure. Sorry. If I think of anything else, I'll post it In the meantime, it would also suck if people started getting more rejected shares... hmmm. I don't, it does work for me, but I encourage everyone to check their results (the actual amount of accepted shares that they get).

[bitless]

Thanks for your code. It's nice to see people get rewarded for their efforts (though it doesn't always happen). Well, I've tried it on my own miner (minerd) and have some very strange findings.

https://forum.bitcoin.org/index.php?topic=21275.0

First of all, minerd supports up to 4 vectors, and when I add this change to my kernel, it actually _slows down_ the 4 vector version. But when I override it to set 2 vectors, it speeds it up. However, once it's sped up, I then get runs of rejected shares. I tried it multiple times with and without and it does appear to be just this change that causes it, so I'm not sure what's going on.

Also, a very silly thing here -> I've posted   #define Ma(x, y, z) amd_bytealign( (z^x), (y), (x) ), but I really should have put all expressions in parentheses. So, ((z)^(x)) and not (z^x) etc.... you know

Regardless. You got me worried about rejected shares. I HIGHLY encourage one of us to go through the truth table in my original post and the C code that was used to generate it to make sure there's no errors. That's why I posted it to begin with. It would really suck if it didn't work.

[czz]

Did not notice any increase in the reject ratio. Using 5870, came from 439 to 449 MH/s.
Many thanks.

[bitless]

Heeey! This change is now in git repository! I'd still parenthesize (z^x) as ((z)^(x)), but regardless, thanks m0mchill and everybody!

https://github.com/m0mchil/poclbm/commit/3d43c4e4c2c476cf367822868202f02d168d6f3b

[themike5000]

Boosted me from 319MH/sec on my 6870 to 326MH/sec.  Not bad.

I"m using GuiMiner v2011-06-09 because v2001-06-14 didn't have a BitcoinMiner.cl file.  Anybody know where to find this file in the newest GUIminer release?

[Kauwi]

I HIGHLY encourage one of us to go through the truth table in my original post and the C code that was used to generate it to make sure there's no errors. That's why I posted it to begin with. It would really suck if it didn't work.

You posted the truth-table (and modified the code) for the MA-function, but your C-code is for the CH-function.
But Your thruth-table for MA-function is correct.

[brunoshady]

not too much increase here in 5850... about 4/5 mhash =(

[ananas5]

Thanks! HD6850 270MHash/s -> 279Mhash/s

[bitless]

I HIGHLY encourage one of us to go through the truth table in my original post and the C code that was used to generate it to make sure there's no errors. That's why I posted it to begin with. It would really suck if it didn't work.

You posted the truth-table (and modified the code) for the MA-function, but your C-code is for the CH-function.
But Your thruth-table for MA-function is correct.

Sorry about the confusion. CH = BFI_INT, since BFI does the same thing as the CH function in the hash spec. MA is built using CH/BFI, so there's a define for CH (copied from and docs) and the MA built on top of CH. Thank you for verifying this stuff. 

[Kauwi]

I HIGHLY encourage one of us to go through the truth table in my original post and the C code that was used to generate it to make sure there's no errors. That's why I posted it to begin with. It would really suck if it didn't work.

You posted the truth-table (and modified the code) for the MA-function, but your C-code is for the CH-function.
But Your thruth-table for MA-function is correct.

Sorry about the confusion. CH = BFI_INT, since BFI does the same thing as the CH function in the hash spec. MA is built using CH/BFI, so there's a define for CH (copied from and docs) and the MA built on top of CH. Thank you for verifying this stuff. 

Ah, i see. Didnt look close enough to the printf();
Sorry for that.

[Keninishna]

woot works for me with guiminer. I edited the kernel.cl file in the phatk directory.

[burp]

10MH improvement, thanks! 

[theunforgiven]

Gigabyte 5850 @ 1000/300 - from 390MHash/s to 400MHash/s with the mod applied.

Got a question, which boolean operator is used to sum all the outputs?

((y),(x|z),(z&x))

"Y" , "X or Z", "Z and X"

xyz| (x|z) | (z&x) | y ? (x|z) ? (z&x)  | Ma
000|   0    |    0    |              ?             |  0
001|   1    |    0    |              ?             |  0
010|   0    |    0    |              ?             |  0
011|   1    |    0    |              ?             |  1
------------------------------------------------
100|   1    |    0    |              ¿             |  0
101|   1    |    1    |              ¿             |  1
110|   1    |    0    |              ¿             |  1
111|   1    |    1    |              ¿             |  1

[BombaUcigasa]

I have rewarded you with half of my increased bitcoin revenue margin, well done sir!