summaryrefslogtreecommitdiffstats
path: root/xmrstak/backend/amd
Commit message (Collapse)AuthorAgeFilesLines
* fix duplicated nonce usagepsychocrypt2018-06-041-3/+4
| | | | | | - avoid that a nonce which not fits to the current job is used (check jobId after start nonce is consumed) - move jobId check into the if condition to get a new bunch of nonces - CPU: add jobId validation after the start nonce is consumed
* fix job consume (possible deadlock)psychocrypt2018-06-042-29/+6
| | | | | | | | | fix #1505 - fix possible deadlock of the executor thread - fix racecondition during the job consumation - remove switch_work in all classes `minethd` - move `consume_work` into `globalStates`
* Fix condition on stellite checkJason Rhinelander2018-06-041-1/+1
|
* Spell checkTony Butler2018-06-047-247/+247
|
* support stellite v4 forkpsychocrypt2018-06-042-8/+16
| | | | | | solve #1494 - add algorithm `cryptonight_v7_stellite` (internal named: `cryptonight_stellite`)
* fix that cli option `--noAMDCache`psychocrypt2018-06-041-6/+6
| | | | - fix that to much OpenCL calls whre used if cache is disabled
* add support for IPBC coinpsychocrypt2018-06-042-7/+16
| | | | | - add algorithm `cryptonight_lite_v7_xor` - update documentation
* remove fork for sumokoin and moneropsychocrypt2018-06-041-1/+1
| | | | remove fork version for sumokoin and monero7
* add independent dev pool coin descriptionpsychocrypt2018-06-043-13/+14
| | | | | | | | | | | | | | - allow the dev pool to fork on a different block version than the user descriped coin All algorithm are centered around the user coin description. It is allowed to have two two different coin algorithms in the user coin description. It is only allowed to use algorithms for the dev pool coin description those are used in the user coin description. There are two ways to define a non forking coin. - set both user coin algorithm descriptions to the same algorithm and set version to zero - set the first algorithm in the user coin description to something you like to use in the dev pool and set the second algorithm to the correct representation of the coin. Set the version to 255. This will allow that the dev pool can mine on a different coin algorithm than the not forking user coin. Do not use an algorithm with different scratchpad size for the dev pool.
* fix wrong algo selectionpsychocrypt2018-06-041-2/+9
| | | | | In the case where the dev pool mines on a higher version than a monero fork coin the miner is not resetting the algorithm. This PR select the correct algorithm each time the block version hash changed.
* allow non AMD OpenCL driver and devicespsychocrypt2018-06-044-13/+47
| | | | | | - add CLI flag to explicitly use non AMD OpenCL and devices - adjust OpenCL output (use OpenCL instead of AMD if --altOpenCL is sued) - optimize NVIDIA OpenCL auto suggestion
* refactor scratchpad creationpsychocrypt2018-06-042-5/+10
| | | | Use the maximum scratchpad size from before and after the fork.
* amd simplify kernel for different algorithmspsychocrypt2018-06-044-431/+295
| | | | | | | - remove version numbers within the kernel - create seperate program context for each mining algorithm - remove kernel `cn1_monero` is now integrated in `cn1` - remname `cnX` kernel in `cnX + algorithmNumber`
* Fix spelling mistake in gpu.cppTakeshi Suzuki2018-06-041-2/+2
|
* Repair all 'namepsace' to 'namespace' (all within comments)Tony Butler2018-06-041-1/+1
|
* AMD OpenCL: fix sumokoinpsychocrypt2018-06-041-3/+12
| | | | - fix that version argument was not passed to extended kernel parameters
* change `height` to `version`psychocrypt2018-06-041-1/+1
| | | | -rename `mining_fork_height` to `*_version`
* refactor mining algo selectionpsychocrypt2018-06-042-21/+14
| | | | | - add `fork_height` to currency - refactor algorithm selection
* fix OpenCl AMD on OSXpsychocrypt2018-06-041-4/+1
| | | | | | fix #1218 - remove inline function with ugly macro :-(
* Add filename to backend errorsfireice-uk2018-06-041-5/+5
|
* POW AEON v7psychocrypt2018-06-042-23/+16
| | | | | - add new pow for AEON - fix missing cryptonight-heavy selection for multi hashes
* add cli option `--noAMDCache`psychocrypt2018-06-041-21/+25
| | | | | | allow to disable the OpenCl cache - usefull for read only systems - usefull for unknown errors during cache reading
* fix parentheses warningpsychocrypt2018-06-041-1/+1
| | | | | | | | | fix warning ``` /Users/user/xmr-stak/xmrstak/backend/amd/amd_gpu/gpu.cpp:481:11: warning: using the result of an assignment as a condition without parentheses [-Wparentheses] if( ret = clGetProgramInfo(ctx->Program, CL_PROGRAM_BINARIES, num_devices * sizeof(char*), all_programs.data(),NULL) != CL_SUCCESS) ```
* Ported xmr-stak 2.3.0 rc to ppc64leJudemir Ribeiro2018-04-012-8/+1
|
* OpenCL precompiled code messagepsychocrypt2018-03-251-3/+3
| | | | change warning when precompiled OpenCL code is not found
* XMR-Stak 2.3.0 RCxmr-stak-devs2018-03-255-57/+371
| | | | | | | Co-authored-by: psychocrypt <psychocryptHPC@gmail.com> Co-authored-by: fireice-uk <fireice-uk@users.noreply.github.com> Co-authored-by: Lee Clagett <code@leeclagett.com> Co-authored-by: curie-kief <curie-kief@users.noreply.github.com>
* fix shadowed variablepsychocrypt2018-03-131-1/+1
| | | | A redefinition of a variable in a local scope avoid that the intensity is rounded to a multiple of the work size.
* add OpenCL compiler cachepsychocrypt2018-03-031-29/+182
| | | | | | | Reduce OpenCL start time by using a self made compiler cache. - store compiled OpenCL binary - load OpenCl binary if available
* fix broken memchunk featurepsychocrypt2018-02-214-4/+4
| | | | fix double definition of define `MEM_CHUNK`
* Merge pull request #1102 from psychocrypt/topic-opencl_1_1fireice-uk2018-02-211-0/+4
|\ | | | | fix compile with OpenCL 1.1
| * fix compile with OpenCL 1.1psychocrypt2018-02-191-0/+4
| | | | | | | | guard error types those are only defined in OpenCL >1.1
* | Merge pull request #1101 from psychocrypt/topic-mesaSupportfireice-uk2018-02-212-3/+26
|\ \ | | | | | | add Mesa OpenCL support
| * | add Mesa OpenCL supportpsychocrypt2018-02-192-3/+26
| |/ | | | | | | allow usage of Mesa OpenCl
* | add OpenCL compatibility modepsychocrypt2018-02-198-16/+48
|/ | | | | - add new option `comp_mode` to the amd config - disable `if guards` within opencl kernel if `comp_mode : false`
* Merge pull request #1087 from psychocrypt/topic-blockedStride3fireice-uk2018-02-198-21/+75
|\ | | | | AMD: option `mem_chunk`and new `strided_index`
| * AMD: `mem_chunk`and new `strided_index`psychocrypt2018-02-178-21/+75
| | | | | | | | | | - add new option for `strided_index` - add additional option if `strided_index == 2` to controll the memory chunk with
* | AMD: reduce register usagepsychocrypt2018-02-141-4/+4
|/ | | | reduce usage of registers: based on the suggestion of @enerc77
* Merge pull request #1013 from psychocrypt/topic-improveAmdAeonAutosuggestionfireice-uk2018-02-031-0/+3
|\ | | | | improve AMD auto suggestion for AEON
| * improve AMD auto suggestion for AEONpsychocrypt2018-01-301-0/+3
| | | | | | | | increase the intensity limit for AEON
* | Merge pull request #1015 from psychocrypt/fix-outputOfAMDGpuNamefireice-uk2018-02-031-1/+1
|\ \ | | | | | | fix output of gpu name
| * | fix output of gpu namepsychocrypt2018-01-301-1/+1
| |/ | | | | | | fix that the GPU name is printed before the name is querried from OpenCL
* | Fix Disabling AMD GPUsRyan2018-02-011-2/+5
|/ | | | | The AMD jconf.cpp would only accept an array. The config sample, and the nvidia and cpu config work with the value 'null', as they accept a 'kNullType'. This means at current, AMD GPUs could not be turned off, the config file wouldn't parse on load. This change makes AMD consistent with the others, and can now be disabled.
* Merge pull request #758 from dougvj/fix_zero_intensityfireice-uk2018-01-271-9/+21
|\ | | | | Add warning and fallback when auto intensity is 0
| * ignore gpu with intensity zeropsychocrypt2018-01-131-18/+17
| | | | | | | | | | - if the intensity is zero than do not suggest a config - remove the links to old issues
| * Add warning and fallback when auto intensity is 0Doug Johnson2017-12-311-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Occassionally the auto adjust doesn't find enough memory and the intensity is detected too low and aligned to 0 with the compute units. This patch fixes this situation by issuing a warning with a suggestion to set environment vars and then ignoring the alignment to 0 Per several issues: Principally: https://github.com/fireice-uk/xmr-stak/issues/81 Related: https://github.com/fireice-uk/xmr-stak/issues/490 https://github.com/fireice-uk/xmr-stak/issues/472
* | remove usage of `rotate`psychocrypt2018-01-241-1/+10
| | | | | | | | revert the change that the OpenCl function `rotate` is used instead of `SKEIN_ROT`
* | author updateGrant Galitz2018-01-241-0/+1
| |
* | Optimize SkeinGrant Galitz2018-01-241-30/+48
| | | | | | | | | | - Eliminate modulus math (It runs slow inside microcode). - Convert whatever the hell was going on into a rotate op. Like... Someone kinda reinvented the wheel in order to do a simple rotate.
* | Merge pull request #848 from psychocrypt/topic-updateVEGANamesfireice-uk2018-01-121-1/+10
|\ \ | | | | | | update VEGA names for auto suggestion
| * | update VEGA names for auto suggestionpsychocrypt2018-01-091-1/+10
| | | | | | | | | | | | update VEGA names
OpenPOWER on IntegriCloud