#Opencl benchmark mac code
Look at the framerate: 1951 FPS (M1 CPU, arm64 native code), 1282 FPS (M1 CPU, x86_64 emulated code via rosetta) and 471 FPS (Intel CPU, x86_64 native code).
#Opencl benchmark mac mac
Here is the same GeeXLab on an Intel-based Mac mini: Rosetta works fine: here, we have GeeXLab compiled for x86_64 architecture running on Apple M1: Rosetta 2 is the new version for the switch from Intel to Apple silicon M1 CPUs. The first version of Rosetta was developed for the switch from PowerPC to Intel CPUs. Rosetta is a translation layer that allows the Apple M1 CPU (arm64 architecture) to execute a x86_64 code developed for Intel-based Macs. Fortunately, it’s easy, you are guided by macOS: On the Apple M1, you can’t launch an x86_64 executable directly. I compiled GeeXLab in two separate versions: GeeXLab for arm64 and GeeXLab for Intel x86_64. This is GeeXLab compiled for arm64 architecture: On Linux, the launch of GeeXLab is fast but on macOS Big Sur + Apple M1, the startup is a bit faster. Once I finished to build GeeXLab, I was impressed by its launch speed: very fast. The arm64-apple-macos11 target is handy if you are on an Intel-based Mac mini and want to compile for ARM architecture. Gcc main.c -o arm_test -target arm64-apple-macos11 If you want to generate a x86_64 code you have to use the following gcc option: By default on Apple M1 + Big Sur, gcc will generate an amr64 code. But in command line with gcc/g++, you have to specify the target architecture. Using Xcode 12.3, you can generate a kind of hybrid executable (Apple calls it an universal macOS binary) that packs the x86_64 and arm64 code. OpenGL is still there in the latest macOS Big Sur! I was surprised to see that all GeeXLab OpenGL code has been successfully compiled. By default, the compilation in command line (like gcc file.c) produces a binary for the arm64 architecture. I installed the latest Xcode 12.3 as well as the command line tools (because gcc/g++ are needed). The source code of GeeXLab is based on makefiles and I had no problem to compile all core libraries from the command line. See THIS PAGE for a more complete TFLOP table. This is more or less the same performance than the Radeon RX 560 or the GeForce GTX 1650:
The M1 GPU has a FP32 performance of 2.6 TFLOPS ( source). The M1 chip is a SoC (System on a Chip) and includes a 8-core CPU, a 8-core GPU as well as other components like a neural engine, memory or input/output interfaces. The utility is free- and a good measure of if you have your graphics working the way they should.Here are some feedbacks about the Mac mini M1 I purchased few weeks ago, in order to compile and test GeeXLab with the new Apple Silicon M1. After Anandtech adoption of SLG as OpenCL benchmark, the code was finally written by David 'Dade' Bucciarelli. The idea was quite simple, wrap SLG inside an easy to use graphical user interface and use it as a benchmark for OpenCL. It was intended as a promotional tool for LuxRender (to quote original Jromang's words: "LuxRender propaganda with OpenCL"). The idea for the program was conceived in 2009 by Jean-Francois 'Jromang' Romang. Post your system's OpenCL benchmarks on OS X using Luxmark. Building a CustoMac Hackintosh: Buyer's Guide
0 kommentar(er)
