qualcomm.com/news/releases/2023/10/…d-wearable-platform-to--wear-os-by- google wants rV android as well. these are good news.

my ryzen 5900 laptop got 415H/s softAes, 706H/s hwAES for 1 thread. so that gives an indication how much these risc-v chips are missing without crypto instructions

hyc is it for the original RandomX or v2?

because v2 has doubled AES

heh, github now has Apple M1 runners: github.blog/2023-10-02-introducing-…os-larger-runner-for-github-actions

But only for Github Team & Enterprise plans (you have to pay $3.67/month at least + $0.16 per minute used by the M1 runner)

I wonder how they got around Apple's licensing restrictions (the minimum time to "rent" an M1 is 24 hours)

Can anyone with Apple M1 or M2 run randomx-tests from github.com/SChernykh/RandomX/tree/aarch64-clear-cache ? It should theoretically fix incorrect hashes with the latest macOS SDK, although it doesn't pass tests on Github runner (but maybe Github runner is just weird).

hyc selsta ^

will test

[84] Hash test 2a (compiler) ... Assertion failed: (equalsHex(hash, "639183aae1bf4c9a35884cb46b09cad9175f04efd7684e7262a0ac1c2f0b4e3f")), function operator(), file tests.cpp, line 974.

sech1: I can give you access to the M1 VM

I think I have login/password somewhere. Are you talking about VM with IP xxx.xxx.xxx.x73 ?

yes

yeap, logged in

I have no idea what's broken, but I'll try to fix it

At least I can iterate faster than with Github CI

ty, would be really nice if this can get fixed

I have the code which cleans the cache properly, now it's all about understanding why even this code doesn't work :D

I thought __builtin__clear_cache was somehow broken in the latest SDK, but it's something deeper

sech1: my numbers were from V1

the actual cache clearing code is so simple, can't imagine that part being broken

maybe we need to look at the source code of something that successfully uses jit, like Safari or whatnot