Bitcoin Forum
January 18, 2018, 08:53:44 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 [38] 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 ... 165 »
  Print  
Author Topic: [ANN]: cpuminer-opt v3.7.10, open source optimized multi-algo CPU miner  (Read 390416 times)
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 05:47:06 PM
 #741

I'm starting to prepare v3.3.4 for release. I will check for new posts before I publish

As it stands there are two changes:

- removed incompatible SW build check to fix problems for users with Westmere class CPUs.
- optimized m7m AES +65%, SSE2 %59%

Edit: This is what v3.3.4 should look like when compiler for and run on westmere. It is not actual
program output because I don't have a westmere CPU.

Code:
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2......YES.
Starting mining without AES-AVX optimizations...
 



Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
1516265624
Hero Member
*
Offline Offline

Posts: 1516265624

View Profile Personal Message (Offline)

Ignore
1516265624
Reply with quote  #2

1516265624
Report to moderator
1516265624
Hero Member
*
Offline Offline

Posts: 1516265624

View Profile Personal Message (Offline)

Ignore
1516265624
Reply with quote  #2

1516265624
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1516265624
Hero Member
*
Offline Offline

Posts: 1516265624

View Profile Personal Message (Offline)

Ignore
1516265624
Reply with quote  #2

1516265624
Report to moderator
1516265624
Hero Member
*
Offline Offline

Posts: 1516265624

View Profile Personal Message (Offline)

Ignore
1516265624
Reply with quote  #2

1516265624
Report to moderator
My9bot
Full Member
***
Offline Offline

Activity: 231


View Profile
June 02, 2016, 05:54:38 PM
 #742

I'm starting to prepare v3.3.4 for release. I will check for new posts before I publish

As it stands there are two changes:

- removed incompatible SW build check to fix problems for users with Westmere class CPUs.
- optimized m7m AES +65%, SSE2 %59%
very nice work
waiting for v3.3.4
thank you a lot

I'm better with code than with words-SatoshiNakamoto
Espers [ESP]SiteOnBlockchain
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 06:34:23 PM
 #743

I'm starting to prepare v3.3.4 for release. I will check for new posts before I publish

As it stands there are two changes:

- removed incompatible SW build check to fix problems for users with Westmere class CPUs.
- optimized m7m AES +65%, SSE2 %59%

Edit: This is what v3.3.4 should look like when compiler for and run on westmere. It is not actual
program output because I don't have a westmere CPU.

Code:
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2......YES.
Starting mining without AES-AVX optimizations...
 

cpuminer-opt v3.3.4 released.

https://drive.google.com/file/d/0B0lVSGQYLJIZVTFNSkZ0elRQZ2M/view?usp=sharing

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
th3.r00t
Sr. Member
****
Offline Offline

Activity: 311



View Profile WWW
June 02, 2016, 08:29:00 PM
 #744

AMD
Code:
         **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        AMD Phenom(tm) II X4 940 Processor
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2.....YES.
YES.
Starting mining without AES-AVX optimizations...
Something is missing there...

Intel
Code:
         **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
   CPU arch supports AES-AVX...YES.
   SW built for AES-AVX........YES.
   Algo supports AES-AVX.......YES.
Start mining with AES-AVX optimizations...

BitSend ◢◤Clients | Source
www.bitsend.info
█▄
█████▄
████████▄
███████████▄
██████████████
███████████▀
████████▀
█████▀
█▀












Your Digital Network | 10MB Blocks
Algo: XEVAN | DK3 | Masternodes
Bitcore - BTX/BTC -Project












BSD -USDT | Bittrex | C.Gather | S.Exchange
Cryptopia | NovaExchange | Livecoin
CoinPayments | Faucet | Bitsend Airdrop













████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████

████
 ████
  ████
   ████
    ████
     ████
      ████
       ████
        ████
       ████
      ████
     ████
    ████
   ████
  ████
 ████
████
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 08:47:39 PM
 #745

AMD
Code:
         **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        AMD Phenom(tm) II X4 940 Processor
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2.....YES.
YES.
Starting mining without AES-AVX optimizations...
Something is missing there...

Intel
Code:
         **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
   CPU arch supports AES-AVX...YES.
   SW built for AES-AVX........YES.
   Algo supports AES-AVX.......YES.
Start mining with AES-AVX optimizations...

Nothing missing just something extra, two answers to the same question.
I'm in no rush to fix it but thanks for pointing it out.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
USScrypto
Hero Member
*****
Offline Offline

Activity: 490

https://nucleus.vision/


View Profile
June 02, 2016, 08:51:26 PM
 #746

L5630 Westmere works just fine with AES-NI and AVX with the latest Win binaries from CMB, performance however seems a bit weird going between 10 and 100 H/s with CPU load being low. Wolfs miner works fine with max load on the CPU...

joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 09:09:25 PM
 #747

L5630 Westmere works just fine with AES-NI and AVX with the latest Win binaries from CMB, performance however seems a bit weird going between 10 and 100 H/s with CPU load being low. Wolfs miner works fine with max load on the CPU...

Is that with hodl? I think your CPU is an Ivybridge based on the date of release.

http://ark.intel.com/products/47927/Intel-Xeon-Processor-L5630-12M-Cache-2_13-GHz-5_86-GTs-Intel-QPI?q=L5630

I think you should be getting around 150 H with 8 threads, have you tried the other bins?

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
USScrypto
Hero Member
*****
Offline Offline

Activity: 490

https://nucleus.vision/


View Profile
June 02, 2016, 09:13:38 PM
 #748

Yes, for HODL. It is a Westmere-EP CPU, not Ivybridge. It is a lower power model and has less hashrate
It only works with cpuminer.exe, the others all crash when I try them including the amd one.

Just rebooted the computer and it seems to work normally again, the cpu load is maxed out and the hashrate is high., will monitor it for a while just in case.
Before rebooting the load was getting to minimum and maximum all the time with cpuminer.exe, but with wolfs miner it was maxing out at 100% and providing normal hashtrate.

Ok it did the same thing again, started at high CPU load and max hashrate, found a couple of shares and then the performance and CPU load started dropping to about 10% of the normal value...

joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 09:30:51 PM
 #749

Yes, for HODL. It is a Westmere-EP CPU, not Ivybridge. It is a lower power model and has less hashrate
It only works with cpuminer.exe, the others all crash when I try them including the amd one.

Just rebooted the computer and it seems to work normally again, the cpu load is maxed out and the hashrate is high., will monitor it for a while just in case.
Before rebooting the load was getting to minimum and maximum all the time with cpuminer.exe, but with wolfs miner it was maxing out at 100% and providing normal hashtrate.

Yours is the first Westmere that reports support for AES and AVX. Did you get all YESes? If so that's another data point in
to the previous problems.

If you got a YES for AES SW build it helps explain the problems some of the other Westmeres have had. Their CPUs say
NO to AES then fail to detect a comtabible SW build. It fails for SSE2 because it's actually AES.

With v3.3.4 the miner will no longer error out in a situation where it believes the CPU does not support AES but the
SW does. It will try to run anyway. If the CPU Is in fact missing AES it will crash. This would also mean that some
westmere's (like yours) support AES and others don't. Still a confusing situation.

This may leave some westmere users without a useable binary for cpuminer-opt unless they compile their own.

Waiting for feedback from them.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
USScrypto
Hero Member
*****
Offline Offline

Activity: 490

https://nucleus.vision/


View Profile
June 02, 2016, 09:32:27 PM
 #750

Yes, I'm getting all YESes with cpuminer.exe

joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 09:41:55 PM
 #751

Yes, I'm getting all YESes with cpuminer.exe

Thanks.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
Roolieman
Jr. Member
*
Offline Offline

Activity: 53


View Profile
June 02, 2016, 10:59:58 PM
 #752

Joblo, can you make Windows version so I can test on Xeon E5649 (Westmere-EP, AES without AVX)

joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 02, 2016, 11:25:45 PM
 #753

Joblo, can you make Windows version so I can test on Xeon E5649 (Westmere-EP, AES without AVX)

Cryptomining Blog has made binaries, follow the link in my sig for details. They have a westmere build.
You should  also try the sandybridge build. I'd like to see your results.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
Roolieman
Jr. Member
*
Offline Offline

Activity: 53


View Profile
June 02, 2016, 11:46:20 PM
 #754

sry just saw it on the first page.

Westmere Xeon E5649 now works fine, 2 CPU's are throwing ~700kH/s (using cpuminer.exe)

Sandybridge build on i5-2500K gets ~250kH/s

Older Xeon's E5540 (Gainestown) with only SSE2 support are starting miner but crashes every time after receiving first data (using cpuminer.exe)

Checking CPU capatibility...
        Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2.....YES.
YES.
Starting mining without AES-AVX optimizations...


Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   cpuminer.exe
  Application Version:   0.0.0.0
  Application Timestamp:   00130158
  Fault Module Name:   cpuminer.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00130158
  Exception Code:   c000001d
  Exception Offset:   00000000000b7bd1
  OS Version:   6.3.9600.2.0.0.272.7
  Locale ID:   1033
  Additional Information 1:   3644
  Additional Information 2:   3644a7a02c1327208b46c488f6992045
  Additional Information 3:   0f4d
  Additional Information 4:   0f4d7611d008af45087a270ad4ae60b1

hmage
Member
**
Offline Offline

Activity: 83


View Profile
June 03, 2016, 01:53:22 AM
 #755

AMD
Code:
        **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        AMD Phenom(tm) II X4 940 Processor
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2.....YES.
YES.
Starting mining without AES-AVX optimizations...
Something is missing there...

Intel
Code:
        **********  cpuminer-opt 3.3.4  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Checking CPU capatibility...
        Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
   CPU arch supports AES-AVX...YES.
   SW built for AES-AVX........YES.
   Algo supports AES-AVX.......YES.
Start mining with AES-AVX optimizations...

Nothing missing just something extra, two answers to the same question.
I'm in no rush to fix it but thanks for pointing it out.


First snippet says no to AES, yes to SSE2, and yes for nothing.

Second snippet says yes to AES, yes to AES, yes to AES.

See that second snippet doesn't mention SSE2 at all?

To avoid user confusion, I suggest you simplify the logic and always display yes/no answers to sse2, aes and avx, like this:
Code:
Checking compatibility of this cpuminer and CPU (Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz)
   cpuminer expects SSE2:           YES.
   cpuminer expects AES:            YES.
   cpuminer expects AVX:            YES.
   CPU supports SSE2:               YES.
   CPU supports AES:                YES.
   CPU supports AVX:                YES.
   requested algo supports AES+AVX: YES.
[2016-06-03 04:53:49] 4 miner threads started, using 'hodl' algorithm.

Diff is here -- https://github.com/hmage/cpuminer-opt/commit/ddcf4d6d5bf2ace2582947eaf9ff565114460f2f

hmage
Member
**
Offline Offline

Activity: 83


View Profile
June 03, 2016, 02:03:35 AM
 #756

By the way, after that patch, I've found a bug:
Code:
Checking compatibility of this cpuminer and CPU (Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz)
   cpuminer expects SSE2:           YES.
   cpuminer expects AES:            no
   cpuminer expects AVX:            no
   CPU supports SSE2:               YES.
   CPU supports AES:                no
   CPU supports AVX:                YES.
   requested algo supports AES+AVX: YES.
[2016-06-03 04:57:04] 4 miner threads started, using 'hodl' algorithm.

See that "CPU supports AVX: yes"? That's a bug in has_avx(). For some reason the code you inherited returns yes if CPU either has AVX or OSXSAVE flag. Fix — https://github.com/hmage/cpuminer-opt/commit/5975fcf2ecad7057a254cc358e55434059124971

cpuid on that machine reports that OSXSAVE flag is supported by this cpu but not AVX:
Code:
$ cpuid -1|egrep -i 'avx|xsave'
      FXSAVE/FXRSTOR                         = true
      XSAVE/XSTOR states                      = true
      OS-enabled XSAVE/XSTOR                  = true
      AVX: advanced vector extensions         = false
      AVX2: advanced vector extensions 2       = false
      AVX512F: AVX-512 foundation instructions = false
      AVX512PF: prefetch instructions          = false
      AVX512ER: exponent & reciprocal instrs   = false
      AVX512CD: conflict detection instrs      = false
   XSAVE features (0xd/0):
         XCR0 field supported: AVX state      = false
         XCR0 field supported: AVX-512 state  = false
      bytes required by XSAVE/XRSTOR area     = 0x00000240 (576)
   XSAVE features (0xd/1):
      XSAVEOPT instruction                        = false
      XSAVEC instruction                          = false
      XSAVES/XRSTORS instructions                 = false
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 03, 2016, 03:25:20 AM
 #757

By the way, after that patch, I've found a bug:
Code:
Checking compatibility of this cpuminer and CPU (Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz)
   cpuminer expects SSE2:           YES.
   cpuminer expects AES:            no
   cpuminer expects AVX:            no
   CPU supports SSE2:               YES.
   CPU supports AES:                no
   CPU supports AVX:                YES.
   requested algo supports AES+AVX: YES.
[2016-06-03 04:57:04] 4 miner threads started, using 'hodl' algorithm.

See that "CPU supports AVX: yes"? That's a bug in has_avx(). For some reason the code you inherited returns yes if CPU either has AVX or OSXSAVE flag. Fix — https://github.com/hmage/cpuminer-opt/commit/5975fcf2ecad7057a254cc358e55434059124971

cpuid on that machine reports that OSXSAVE flag is supported by this cpu but not AVX:
Code:
$ cpuid -1|egrep -i 'avx|xsave'
      FXSAVE/FXRSTOR                         = true
      XSAVE/XSTOR states                      = true
      OS-enabled XSAVE/XSTOR                  = true
      AVX: advanced vector extensions         = false
      AVX2: advanced vector extensions 2       = false
      AVX512F: AVX-512 foundation instructions = false
      AVX512PF: prefetch instructions          = false
      AVX512ER: exponent & reciprocal instrs   = false
      AVX512CD: conflict detection instrs      = false
   XSAVE features (0xd/0):
         XCR0 field supported: AVX state      = false
         XCR0 field supported: AVX-512 state  = false
      bytes required by XSAVE/XRSTOR area     = 0x00000240 (576)
   XSAVE features (0xd/1):
      XSAVEOPT instruction                        = false
      XSAVEC instruction                          = false
      XSAVES/XRSTORS instructions                 = false


I need to make two points. In v3.3.4 the checks are all non-enforcing, regardless of the results
of the capabilities check. Without a Westmere of my own to test with I need to know how it really works
so I had to make it permissive and risk the miner crashing.

Yes you found a bug, mine by the way. I just assumed the AVX1 flag was what it says. It could result in a false positive
CPU AES check only if the CPU has AES but not AVX. If the CPU does not have AES the false AVX reading has no effect.
This bug may have a bearing on the Westmere problem but is no worse than the previous check that only read the
AES bit of CPUID.

I need to fully understand the architecture of Westmere as well as why the __AES__ macro seems to return different
results on different CPUs with the same SW build. The problem with westmere CPUs is all about the __AES__ macro.

I repeat it's all about the __AES__ macro on Westmere CPUs using the Westmere binary. At this point I don't really care
what the flags say, I just want the miner to work on Westmere. Once the Westmere architecture is characterized  and
if the __AES__ discrepency is understood, only then will I think about revisiting the flags. I've already broken enough
shit with my inability to test on Westmere. These guys need a working build.

The key questions are:

1. Are there two versions of Westmere CPUs with differing support for AES and AVX but using the same compile arch.

2. Was the CMB Westmere build compiled natively on Westmere or crosscompiled using -marh=corei7.

3. What CPU capabilities does the corei7 compile arch support and is it compatible with all Westmere CPUs.

I need those questions answered before trying anything else.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 03, 2016, 03:28:57 AM
 #758


First snippet says no to AES, yes to SSE2, and yes for nothing.


Wrong. First snippet says yes to AES CPU, second snippet says YES to SSE2 CPU,
third snippet say YES to SSE2 CPU again.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 03, 2016, 03:41:31 AM
 #759

sry just saw it on the first page.

Westmere Xeon E5649 now works fine, 2 CPU's are throwing ~700kH/s (using cpuminer.exe)

Sandybridge build on i5-2500K gets ~250kH/s

Older Xeon's E5540 (Gainestown) with only SSE2 support are starting miner but crashes every time after receiving first data (using cpuminer.exe)

Checking CPU capatibility...
        Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
   CPU arch supports AES-AVX...NO.
   CPU arch supports SSE2.....YES.
YES.
Starting mining without AES-AVX optimizations...


Thank you for your testing, the crash of Gainstown is expected because it has no AES whatsoever. This proves
the Westmere build is not compatible with core2, another significant data point.

cpuminer-opt does work on core2 on linux (all algos) and Windows (all except hodl). This I have tested. You will
either have to compile your own with -march=native or ask CMB to do it for you.

Can you post the capabilities check results from the Westmere CPUs?

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
joblo
Legendary
*
Offline Offline

Activity: 1008


View Profile
June 03, 2016, 05:35:06 AM
 #760

By the way, after that patch, I've found a bug:
Code:
Checking compatibility of this cpuminer and CPU (Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz)
   cpuminer expects SSE2:           YES.
   cpuminer expects AES:            no
   cpuminer expects AVX:            no
   CPU supports SSE2:               YES.
   CPU supports AES:                no
   CPU supports AVX:                YES.
   requested algo supports AES+AVX: YES.
[2016-06-03 04:57:04] 4 miner threads started, using 'hodl' algorithm.

See that "CPU supports AVX: yes"? That's a bug in has_avx(). For some reason the code you inherited returns yes if CPU either has AVX or OSXSAVE flag. Fix — https://github.com/hmage/cpuminer-opt/commit/5975fcf2ecad7057a254cc358e55434059124971


I looked into this a bit more and there is more to this bug than I first thought. The way the flags are defined is illogical
and does not agree with the wikipedia reference with no explanation for the discrepency. The coding does not seem
like a typical error. That's not the kind of definition you do by mistake. This bizarre definition also applies to the FMA3
flag. These flags are used in best_cpu_feature function so one would think that if anyone ever used that function
they might have noticed some bizarre results.

That is all to say there might be some legitimacy to the way the flags are defined. I noted in the wikipedia article that
the bit definitions were as of 2011. This suggests that the flags were different prior to 2011 which includes westmere.

Even if the coding is legitimate I would not have done it that way. I woul dhave defined the bits individually and
only used the compound expression when they were being read.

I'm not convinced it is a bug. It may be a relic of a previous CPUID format. But it's a moot point because I don't intend
to revisit this issue without a breakthrough.

Principal developer of cpuminer-opt, the optimized multi-algo CPU miner.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
https://bitcointalk.org/index.php?topic=1326803.0
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 [38] 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 ... 165 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!