Re:Building Elixir from source segfaults on macOS on Apple S...
by ArgyleSound on Monday July 13, 2020 @03:47PM
(#23824846)
Would it would work under Rosetta 2 (Apple's x64 emulation/translation layer) until the aarch64/darwin ABI can be ported to GCC? Or is there a reason to assume it might not?
[ Parent
| on HN ]
Re:Building Elixir from source segfaults on macOS on Apple S...
by KenoFischer on Monday July 13, 2020 @03:58PM
(#23824940)
Yes, it works mostly fine under Rosetta. However, it is also precisely the area where you don't really want a translation layer, because you're spending a lot of time doing heavy compute.
Re:Building Elixir from source segfaults on macOS on Apple S...
by ArgyleSound on Monday July 13, 2020 @04:02PM
(#23824978)
That makes sense. I'm hoping it's going to be an early adopter problem that'll have been solved by the time the transition is deemed complete.
Re:Building Elixir from source segfaults on macOS on Apple S...
by sitkack on Tuesday July 14, 2020 @03:44AM
(#23829501)
Many compute heavy tasks are using Metal and those should continue to function at the full speed of the hardware.
Re:Building Elixir from source segfaults on macOS on Apple S...
by pritambaral on Tuesday July 14, 2020 @09:18AM
(#23831560)
I doubt GCC is, or even could be, using Metal.
Re:Building Elixir from source segfaults on macOS on Apple S...
by sitkack on Tuesday July 14, 2020 @01:14PM
(#23834715)
I am referring to modern HPC like workloads, they will be using the GPU. Not saying GCC is using Metal in any way whatsoever.
Re:Building Elixir from source segfaults on macOS on Apple S...
by pritambaral on Tuesday July 14, 2020 @01:36PM
(#23835031)
HPC on macOS? Using Metal instead of CUDA/OpenCL? Sounds extremely rare.