Bug 78163 - xpmclminer with multiprecision math return wrong results on Turks OpenCL
Summary: xpmclminer with multiprecision math return wrong results on Turks OpenCL
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Tom Stellard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 99553
  Show dependency treegraph
 
Reported: 2014-05-01 17:19 UTC by Alexey Shvetsov
Modified: 2019-09-18 19:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Alexey Shvetsov 2014-05-01 17:19:03 UTC
Opencl app that uses multiprecision math gives wrong results

App is https://github.com/eXtremal-ik7/xpmminer


$ ./xpmclminer -b --opencl-platform Mesa
OpenCL platform available: Mesa
8 warnings generated.
8 warnings generated.
[0] AMD TURKS; 1 compute units
[1] AMD TURKS; 1 compute units
 * GPU 1 benchmark start:
Multiply 256 bits CPU time: 4.868, GPU time: 4.131 (1.178 times faster)
element index: 0
gmp: 79016B22 1C710C4A DF86F5C0 18E693EF D677434D 28B50A0A 4A2F8F5E 6FF1E1A6 C17B67E2 77B8CB65 8BA0DF48 3CD297F7 AD74948C 6B99D76B 8A81F331 DF8A45CB 8869E036 825665FF 9505CD30 543C80C6 96E3B1A5 72CE6A4A CEA9324B 7C37E23C 
gpu: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
results differ!
Multiply 384 bits CPU time: 9.280, GPU time: 15.885 (0.584 times faster)
Comment 1 GitLab Migration User 2019-09-18 19:16:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/508.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.