Support for ARM64 Architecture

[nicolas-tallet]

I don't seem to be able to compile FIRESTARTER on a CG4-based system with ARM64 processors.
Is it planned to have ARM64 support anytime soon?

[hoehlig]

FIRESTARTER/include/firestarter/Firestarter.hpp", line 134: catastrophic error: #error directive: "FIRESTARTER is not implemented for this ISA"
  #error "FIRESTARTER is not implemented for this ISA"
   ^

[rschoene]

Hi, we opened a branch. But we use an external repository named asmjit to create the executed workload on runtime. To create a reasonable stress workload for FIRESTARTER, we would need asmjit to support the SVE extensions. If you (or your company) has some money to spare, please reach out to the developer. Here is how: https://kobalicek.com/services.html

[rschoene]

In the current branch, there is a first draft for a NEON-based workload. It is based on the SSE2 workload, not polished and needs to be cleaned up, but it should run. Since it only uses a small part of the processor (NEON Add), do not expect a high power consumption.

[nicolas-tallet]

Thanks @rschoene - we are going to give a try to the ARM64 implementation.

[rschoene]

@nicolas-tallet you're welcome. Please remember that FIRESTARTER will not lead to a very high power consumption. Since, you know, the missing SVE and stuff. On the plus side, you can create an ARM FIRESTARTER_CUDA.

[rschoene]

@nicolas-tallet @hoehlig i changed the default workload. it should be a bit better now, but still no SVE, hence another pointer to https://kobalicek.com/services.html .

[rschoene]

@nicolas-tallet @hoehlig i changed the default workload. it should be a bit better now, but still no SVE, hence another pointer to https://kobalicek.com/services.html .

@nicolas-tallet @hoehlig I forgot to push one file. hence the old workload had been active until now m(

[hoehlig]

Thanks for the effort @rschoene !

[rschoene]

• integrate style
• Clean up code.
  • find cache sizes on the fly
  • implement validity check
  • find a substitute for family/code for Arm
  • Use optimized defaults
• find and fix bugs(?) Ctrl+C ?