Develop Mac versions of solutions for a few labs

[dendibakh]

Currently the following labs don't have solutions for Mac M1 platform:

  ["memory_bound"]["huge_pages_1"]          - need to check huge pages on Mac
  ["misc"]["io_opt1"]                       - mmap on Mac
  ["core_bound"]["compiler_intrinsics_1"]   - NEON version
  ["core_bound"]["compiler_intrinsics_2"]   - NEON version

This prevents automated benchmarking of their speedups in CI.

[andrewevstyukhin]

You can try to use "sse2neon"

[dendibakh]

You can try to use "sse2neon"

Thanks! Good idea.

[Cosmin-B]

Hi @dendibakh, I can confirm that using sse2neon to solve the ["core_bound"]["compiler_intrinsics_1"] does work, albeit it is a bit slower than writing pure ARM Neon code, due to the differences in the architectures and the more instructions need to translate from SSE to NEON using the same x86 algorithms.

You can check the CI Job as well as my branch with commits .

Once again, thank you for the excellent work!

[Cosmin-B]

Ups, I did not mean to close this. Denis, can you please re-open this?

[dendibakh]

Hi @dendibakh, I can confirm that using sse2neon to solve the ["core_bound"]["compiler_intrinsics_1"] does work,

This is nice to know! I haven't used sse2neon before.

albeit it is a bit slower than writing pure ARM Neon code, due to the differences in the architectures and the more instructions need to translate from SSE to NEON using the same x86 algorithms.

I can't find your NEON implementation. Can you please share it?

Once again, thank you for the excellent work!

You're welcome! :)

[Cosmin-B]

Hey @dendibakh

This is it! implementation. You can look at the history as well as see that I added the sse2neon.h in the compiler_intrinsics_1 folder. You can add that as a dependency that you would pull automatically on ARM devices compatible with Neon.

Additionally, here is the link to the CI job for M1 Mac, I had to enable the CI to run on M1 for this lab, I did that here.

P.S.: I am sorry for temporarily closing the issue again. The GitHub interface is not friendly enough for me.

Kind regards,
Cosmin

[dendibakh]

I thought you said you wrote NEON instrinsics yourself without using sse2neon library, no?

[Cosmin-B]

I can confirm that using sse2neon to solve the ["core_bound"]["compiler_intrinsics_1"] does work, albeit it is a bit slower than writing pure ARM Neon code

Hey, @dendibakh, I am sorry for the misunderstanding. However, I did not say that. I only said that I confirmed that it could be done using the sse2neon library.

Kind regards,
Cosmin

[dendibakh]

I can confirm that using sse2neon to solve the ["core_bound"]["compiler_intrinsics_1"] does work, albeit it is a bit slower than writing pure ARM Neon code

Hey, @dendibakh, I am sorry for the misunderstanding. However, I did not say that. I only said that I confirmed that it could be done using the sse2neon library.

Kind regards, Cosmin

Ok, got it, no worries. Thanks for sharing your experiments.