arkivm

A month for a one-liner fix? Why don't you make the porting guide PR-able?

No upstream issue found. But I found this https://github.com/browsertron/pytest-parallel/issues/93 which suggests a [fix](https://stackoverflow.com/a/52230415). I tested with the below patch. Test passes fine on `aarch64-darwin`. ``` diff --git a/pkgs/development/python-modules/debugpy/default.nix b/pkgs/development/python-modules/debugpy/default.nix index...

Thanks for checking @fmoda3. Also, let's unset `OBJC_DISABLE_INITIALIZE_FORK_SAFETY` in `postCheck`

@toor1245 does it work on aarch64-darwin by any chance? I tried running it, it hits an "illegal instruction".

Btw, if this gets merged, are we going to drop all the OS APIs (e.g., `sysctl`) for arm64 and switch to this version?

@toor1245 ```c __asm__ volatile ("mrs %0, cntvct_el0" : "=r" (cntvct1)); // works __asm__ volatile ("mrs %0, tpidrro_el0" : "=r" (tpidr)); // works __asm__ volatile ("mrs %0, midr_el1" : "=r" (midr));...

No problem. Thanks for the great work. As numerous projects started tagging that they depend on this, I decided to push it forward.

As @sbehnke did all the work, can someone tell me how to add something like Linux's `Co-developed-by` tag to a github PR? I would like @sbehnke to sign off this...

> Looks good on my M1 Max. Great. Thank you for quickly testing it.

> I don't see the `__arm64__` macro for `CPU_FEATURES_ARCH_AARCH64` in `cpu_features_macros.h`? This macro is used for iphone added this as well.