[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[integrale]

i havent noticed on other algos , i know timetravel is changing    and i have also tested several times to confirm the loss for my own   changing miner version in time gaps of some second many time  it ranges in between 8-10% lower hashrate on 3.5.10 compared to  3.5.9  because of this im using the faster one only for that type of cpu . (3 pcs. of Athlon II x2 240 , 250 255 ) the peak delivered hashrate is between 126 - 140 kh/s
if it helps you i can test other algos of your choice , let me only know wich one´s   i´ll report then

[joblo]

I've created a pull request to add support for onecoin (OC):

https://github.com/JayDDee/cpuminer-opt/pull/5

Coin:
https://bitcointalk.org/index.php?topic=1801129

I've looked at your pull request. I would normally take the code and implement it in my own environment
then upload it to git but I'm willing to let git do the merge, but there are a couple of small changes
needed.

1. I like to keep the algos in alphabetical order, so sha256t would be listed after sha256d everywhere.

2. sha256t.c source file should be in algo/sha2/, same place as little brother.

3. It may be desireable to include the coin name and symbol in the help text, and fix the text alignment.

I can easilly make the changes and merge the algo into my 3.5.12 dev stream and it will get released
in the normal course. Nothing else to release yet so it may be a few days.

Or, you can make the changes and resubmit the pull request and I will merge it immediatly in git.
Either way works for me.

Edit: one more thing, the algo_not_tested warning in register_sha256t_algo. You can remove it if you've
tested it yourself, or leave it in until the coin goes live and gets field tested. Your call.


Edir Nevermind. I've got it coded and it works, will be in 3.5.12, missed 3.5.11 by less than a day.

[joblo]

i havent noticed on other algos , i know timetravel is changing    and i have also tested several times to confirm the loss for my own   changing miner version in time gaps of some second many time  it ranges in between 8-10% lower hashrate on 3.5.10 compared to  3.5.9  because of this im using the faster one only for that type of cpu . (3 pcs. of Athlon II x2 240 , 250 255 ) the peak delivered hashrate is between 126 - 140 kh/s
if it helps you i can test other algos of your choice , let me only know wich one´s   i´ll report then

I misunderstood, the delta was in 3.5.10 vs 3.5.9. 3.5.10 did have some changes that would affect Timetravel.
I only tested performance on AVX2. the changes may have had a negative effect on older CPUs.
I'll do some more testing.

[integrale]

as i remember you changed some memory things    because of the Stack-smashing   to avoid crashes in 3.5.10  maybe that makes some algos slower , that affects the miner reponse is slower to find accepted hash , its really not easy to detect all difference on my testing-tour   uffff allways coming new one to the daylight

[joblo]

as i remember you changed some memory things    because of the Stack-smashing   to avoid crashes in 3.5.10  maybe that makes some algos slower , that affects the miner reponse is slower to find accepted hash , its really not easy to detect all difference on my testing-tour   uffff allways coming new one to the daylight

Yes, I converted some memory accesses to use SSE2 instructions. If those instructions are less efficient on AMD x2
it could be slower.

If that's the case and it is faster on newer CPUs I don't want to trade that speed  for an old AMD architecture.
I haven't tested yet, so we'll see.

[integrale]

no need to change something , only inform in the OP-page those user of this type of cpu   
because  hard enough any change

take it only as my advice

[denravonska]

the algos which gonna fail

miner stops after checking first block , crash is then reported by miner as illegal instruction

3.5.11 tested , same results as in 3.5.10 nothing changes for Amd cpu

Thanks for testing. I think I've done all I can to get thosre old AMDs to work.

An illegal instruction usually means the CPU hasn't implemented it, often when trying to
ue AES instructions on a CPU that doesn't support AES. In this case it appears these AMD
CPUs don't have the full SSE2 implementation.

Even if there was a way for the compiler to detect this condition the result would be a build
without any optimizations, ie it would be the same as cpuminer-multi.

My recommendation is to use cpuminer-multi on those algos.

Oh, I didn't realize my Athlon64 was _that_ old, failing at SSE3 instructions. Reverting back to 3.4.12 then

[joblo]

Which is better on x2, 3.4.12 or 3.5.9?

[integrale]

i would use 3.5.9 because of more algos implemented , my opinion


btw. the link you provided is a master release

looks like hmq1725 not included

Code:

./cpuminer -a hmq1725 -t 2 -o stratum+tcp://yiimp.ccminer.org:3747 -u BCuFcijYuwgn4oFzo3ZVecebdrw2C7Fbqy -p x,c=BOAT,stats
** cpuminer-multi 1.1-git by Tanguy Pruvot (tpruvot@github) **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd

[2017-03-01 18:29:07] Unknown algo parameter 'hmq1725'
Try `cpuminer-multi --help' for more information.
sklave@miner3-HP-500B:~/hmq1725$ 

im giving up for now searching this algo

[joblo]

i would use 3.5.9 because of more algos implemented , my opinion


btw. the link you provided is a master release

looks like hmq1725 not included

Code:

./cpuminer -a hmq1725 -t 2 -o stratum+tcp://yiimp.ccminer.org:3747 -u BCuFcijYuwgn4oFzo3ZVecebdrw2C7Fbqy -p x,c=BOAT,stats
** cpuminer-multi 1.1-git by Tanguy Pruvot (tpruvot@github) **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd

[2017-03-01 18:29:07] Unknown algo parameter 'hmq1725'
Try `cpuminer-multi --help' for more information.
sklave@miner3-HP-500B:~/hmq1725$ 

im giving up for now searching this algo

LOL. Ocminer likes to take shortcuts and reuse existing algo names, I think he used quark for this one.
Check the instructions at suprnova to be sure.

[integrale]

ok  thanks for the tip   last try 

[integrale]

i must be a superhuman and  magician  if i can read something from a white blank page   LOL  or they hiding something from us



edit : just tried "quark "    works 

[th3.r00t]

Which is better on x2, 3.4.12 or 3.5.9?

Generally on all AMD's without AES/AVX, v3.4.12 produce higher hashrates than newer v3.5.x branch.
If there is AES/AVX support on AMD CPU newer v3.5.x branch is better.

[joblo]

Which is better on x2, 3.4.12 or 3.5.9?

Generally on all AMD's without AES/AVX, v3.4.12 produce higher hashrates than newer v3.5.x branch.
If there is AES/AVX support on AMD CPU newer v3.5.x branch is better.

Thanks. How about broken algos? Any difference?

I'm thinking of updating the legacy branch and
want it to have the most working algos. Restoring the 3.4.12 SSE2 performnace is the easy part.
Tiptoeing through the bug fixes and regressions is a little trickier. I want to chose the legacy base
(3.4.12 or 3.5.9) to make it easier. Find one algo that works on one but not the other and we have
a winner.

Plans for the legacy branch:

- updated no sooner than after 3.5.12 is released, master branch always has priority
- port new algos
- port bug fixes
- maintain the SSE2 groestl performance of 3.4.12
- have the most working algos

Any update to the legacy branch can be considered the last, so ity's a good idea to get it right.

[integrale]

3.5.9
timetravel
lyra2z
deep ?
im voting for 3.5.9

[joblo]

Hello,
I've got this error when compiling on osx:

algo/argon2/ar2/sj/scrypt-jane-portable-x86.h:316:3: error: unknown token in expression
                a2(mov [%1 + 12], edx)

Really appreciate for any helps.
Thanks & Regards.

cpuminer-opt doesn't support osx.

[joblo]

The following post went right over my head at the time. I was a bit distracted with other issues
and didn't realize you were referring to a file in cpuminer-opt.

I presume you were suggesting I update it and you were providing me with a suitable replacement.
I'm not familiar with docker but if it works for you, that's good enough for me. It can't be worse
that what's there now.

But I'm concerned about the first line. It seems to tie it to Ubuntu 16.04. Can it be made generic?

Thanks.

The Dockerfile in the repo is horribly out of date so I created one for my use.

Code:

FROM ubuntu:16.04
RUN BUILD_DEPS="build-essential \
	libssl-dev \
	libgmp-dev \
	automake \
	git" && \

	apt-get update && \
	apt-get install -y ${BUILD_DEPS} libcurl4-openssl-dev libjansson-dev && \
	git clone --depth 1 https://github.com/JayDDee/cpuminer-opt.git && \
	cd cpuminer-opt && \
	./autogen.sh && \
	CFLAGS="-O3 -march=native -s -Wall -Wl,--build-id=none" \
	CXXFLAGS="$CFLAGS -std=gnu++11 -fpermissive" \
	./configure --with-curl --with-crypto && \
	make -j $(nproc) && \
	make install && \
	apt-get remove -y ${BUILD_DEPS} && \
	apt-get autoremove -y && \
	rm -rf /cpuminer-opt

ENTRYPOINT ["/usr/local/bin/cpuminer"]
CMD ["-h"]

[g1itch]

Why don't you create a branch on github for the legacy 3.4 branch?

[felixbrucker]

The following post went right over my head at the time. I was a bit distracted with other issues
and didn't realize you were referring to a file in cpuminer-opt.

I presume you were suggesting I update it and you were providing me with a suitable replacement.
I'm not familiar with docker but if it works for you, that's good enough for me. It can't be worse
that what's there now.

But I'm concerned about the first line. It seems to tie it to Ubuntu 16.04. Can it be made generic?

Thanks.

The Dockerfile in the repo is horribly out of date so I created one for my use.

Code:

FROM ubuntu:16.04
RUN BUILD_DEPS="build-essential \
	libssl-dev \
	libgmp-dev \
	automake \
	git" && \

	apt-get update && \
	apt-get install -y ${BUILD_DEPS} libcurl4-openssl-dev libjansson-dev && \
	git clone --depth 1 https://github.com/JayDDee/cpuminer-opt.git && \
	cd cpuminer-opt && \
	./autogen.sh && \
	CFLAGS="-O3 -march=native -s -Wall -Wl,--build-id=none" \
	CXXFLAGS="$CFLAGS -std=gnu++11 -fpermissive" \
	./configure --with-curl --with-crypto && \
	make -j $(nproc) && \
	make install && \
	apt-get remove -y ${BUILD_DEPS} && \
	apt-get autoremove -y && \
	rm -rf /cpuminer-opt

ENTRYPOINT ["/usr/local/bin/cpuminer"]
CMD ["-h"]

the first line tells docker to use the ubuntu 16.04 image as a baseline to build the image
think of the dockerfile as a recipe on how to setup a machine

[joblo]

cpuminer-opt v3.5.12 is released with support for sha256t, 29% faster than ocminer version.

Also renamed lyra2zoin algo to lyra2z330. There is now another coin using this algo.
lyra2zoin and zoin will still work as aliases of lyra2z330.