During the initialization of the compile parameter for OpenCL it could be that the
fixed size buffer is to small. To avoid this we are now using `std::string`.
There is no problem by using `std::string` because this part of code is not perfromance critical.

xmr-stak has several implementations for multi hash per thread.
The results into 3 intepedent implementations.
Each time the algorithm must be changed the possibility to introduce errors is very large.

- unify the different cryptonight CPU implementations
- simplify the function selection array to find the specilized cryptonight implementation
- add a intermediat pointer to access the large state (similar to the old multi hash implementation)

As side effect this change increases the speed of the single and multi hash algorithm.

The most algorithm currently are not checked in the cpu self test function.

- add hash for each algorithm

Improve the grammar of the Dev donation setting.

The coint type was set to a fixed value in one of the last released and has no meaning since we support many cryptonight coins.

- remove cointtype from version.cpp

OpenCl 1.2.is not allowing the subscript operator on buildin vector types.

fix: use `.sX` to access vector components

5% more hash per second

- add cryptonight_heavy derivate cryptonight_bittube2
- add coin bittube
- remove coin ipbc because this coin is now called bittube

fix #1708

The extension of the job result contains the wrong algorithm used to create the nonce.
The fix provide now the correct used algorithm even if the coin is forking to a new algorithm.

- forward the used algorithm from the miner

- remove all cryptonight coins (algorithm cryptonight can still be used)
- update README.md

- add ryo currency
- update documentation

- explicit loop unrolling

based on changes in @imperdin fork https://github.com/imperdin/xmr-stak/blob/master/xmrstak/backend/amd/amd_gpu/opencl/cryptonight.cl

- update pools.txt
- add new algorithm `cryptonight_haven`
- update all backends

- rename cryptonight_fast to cryptonight_masari
- set dev pool to cryptonight_monero

version prepere for the next release

The define of `_mm256_set_m128i` is not needed and avoid intel compiler throws a warning about it.

- 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

The login result of a pool contains the first job for the miner.
In the case where the pool is sending very fast after the pool login result
a new job it is possible that the newer job is processed faster than the job within the login result.
The result will be that the miner is mining an older job instead the newest (last received).

- enumerate all received messages
- trace the message id of the last procssed job
- skip all jobs where the message id is older than the last procesed id

If CUDA 9.X is used and the miner is compiled for `sm_70` and used with Volta GPUs than the miner
deadlocks if `threads` is not a multiple of `32`.

- use `__activemask()` to get all active lanes

- reformat `read_write_lock.h`
- fix spelling issue
- move job id increase of the write to the buttom

user read write locks to be sure that no job is consumend during the job update

add log class from Will Zhang:

Package: cpputil
Source: https://github.com/willzhang4a58/cpputil
License: MIT License

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`

Some pools or proxys are sending multiple times in row the same job to the miner.
This PR will extent the miner to trigger an socket error if job with the same `jobID` than the current active job is received.

Move motd evaluation before the possibil part where a job is ignored.

Trigger event with a new job after the current pool job is updated.

Now able to access behind a reverse proxy.

- initialize miner_work iPoolId in the default constructor with the invalid pool id
- move definition of `pool_data` into an own file