NVIDIA: rename config option `comp_mode` 

fix right bitshift in `amd_bitalign`

CUDA: fix invalid results

The name `comp_mode` for a memoy load pattern if a bad choosen name.
Therefore I changed it to `mem_mode` which also gives use the possibility
to add new mode later if needed.

- rename `comp_mode` to `mem_mode`
- fix documentation

In the current implementation the bit align is using signed integer which results in pulling in
ones in the case the sign bit is set.

- cast to unsigned integer before using bitshift

If `comp_mode` is false the results on a windows platform will be invalid.
The reason for that is that `ulong4` is in windows 16byte and in linux 32byte.

thx @xmrig for finding and solving the issue

fix #1873

Add Ryo sponsorship message

CUDA: select hash function from array

CUDA: use volatile pointer

compatibility and better messages

Add a suggestion to an common line which is shown in the event of an crash under windows.

Add compatibility mode for CUDA to avoid invalid shares.

Use an array  instead of a if cascade to select the hasing function for CUDA.

- add more descriptive messages if memory allocation fails
- add gnu compiler flags: `noexecstack` to support systemd
- handle cases where memroy allocation fails

Co-authored-by: Tony Butler <spudz76@gmail.com>

Use volatile pointer to be sure that the compiler is not caching the values.

CPU: fix logical error

Fix wrong warning about unknown ASM type

OpenCL: fix definition range for unroll

fix crash with monero and strided_index

Strided index 1 is not allowed for cryptonight_v8 and monero.
In the case the dev pool is set to monero and the user tuned there settings for
an other currency the miner will crash if strided index or memChunk is not
fitting the requirement to mine monero.
This PR detects wrong configurations and will set strided index and memChunk to a valid
value but only for cryptonight_v8. The user pool settings will only be changed if monero or
cryptonight_v8 is selected.

Fix two new warnings within new code

fix #1870

- remove zero from the valod definition range for the loop unroll option

fix invalid shares

CUDA: tine cryptonight_v8

fix wrong option in config.tpl

rework all currencies

add cpu family and model detection

With rocm we fighted very long with invalid shares. This is now solved with rocm 1.9 and
this tiny fix.
It is not fully clear where a memory optimization is kicking in and break the kernel `Groestl` if the variables `M` and `H` are not `volatile`.
The performance ill not change with this fix.

The fix is tested with rocm 1.9 with a VEGA64 and a RX570

Read memory in bigger chunks per thread to increase the used memory bandwith.
Use for Kepla and Fermi GPUs the old autosuggestion instead of the new settings for cryptonight_v8.

In #1839 the option for slow memory is sneaky changed. This can lead into crashes on linux systems where the user is not allowed to use large pages.

Helper functions to select the asm version based on the number of used hashes per threads and the family name of the cpu.

- use the noew cpu type functions to fix the wrong AMD family detection in `autoAdjust.hpp`
- allow to set the asm version to `auto`
- rename asm option `intel` to `intel_avx`
- rename asm option `ryzen` to `amd_avx`

Co-authored-by: fireice-uk <fireice-uk@users.noreply.github.com>

spelling+typo touch-ups

whitespace trims

- introduce monero oct 2018 fork as currency `monero`
- remove monero7
- change all dev pools
  - those miner monero7 to handle the fork to monero
  - if the dev pool can not handle the fork to monero the currency is fixed set to `monero` (we can only handle 2 different currencies for user and dev pool)
- remove guards those prevent to use the currency `monero`

cryptonight_v8 version 2

AMD: remove unused functions