-
gingeropolous
lol... no worries.
-
cohcho
Is it possible to launch 64-bit termux within 32-bit Android?
-
sech1
Is it possible to launch any 64-bit app on 32-bit Android?
-
cohcho
cpu should be 64-bit here
-
cohcho
I suppose that user space binary can use 64-bit asm
-
sech1
There's AArch64 execution state and AArch32 execution state. 64-bit state can run 32-bit code, but not the other way.
-
sech1
-
cohcho
I've tried to find simple asm source to compile and test on the phone.
-
cohcho
It would be some kind of runtime check
-
cohcho
aarch64 specific asm *
-
cohcho
But didn't find anything
-
tevador
aarch32 OS cannot host an aarch64 userspace application
-
cohcho
The phone isn't rooted therefore I don't know for sure what OS is being running. I'm trying to test it in runtime
-
cohcho
If you're right then I'll see any error
-
tevador
install CPU-Z from the playstore and go to System Tab
-
tevador
you'll see either aarch64 or armv7l
-
cohcho
armv8l
-
tevador
that's 64-bit
-
cohcho
Therefore I'm continue my road to compile runtime test
-
cohcho
it's likely not reliable test
-
tevador
I take it back, it looks like the 32-bit mode is called armv8l sometimes
-
tevador
should say aarch64 in 64-bit mode
-
cohcho
-
cohcho
the same way as you did in c++ to test hardware aes support in runtime?
-
cohcho
because hello wrold without aes is running fine here
-
cohcho
or even better just static randomx-benchmark build for aarch64
-
cohcho
I've added 3 instructions from randomx-benchmark and it works fine:
paste.debian.net/hidden/c0786122
-
cohcho
Unfortunately, there is no static randomx-benchmark for aarch64 on github
-
cohcho
all runtime tests have passed
-
tevador
good, so you have a 64-bit ARM chip with crypto extensions
-
cohcho
but that android app says armv8l
-
cohcho
and termux is a shitty enviroment
-
cohcho
the same level as cygwin
-
sech1
can't you just try to compile xmrig in termux?
-
cohcho
I'm going to cross-compile for aarch64
-
cohcho
xmrig didn't even compiled due to lack of some headers
-
sech1
works on my android phone, but it's 64 bit
-
cohcho
xmrig hasn't been compiled due to errors *
-
tevador
randomx-benchmark won't compile?
-
cohcho
I've compiled randomx-benchmark successfuly in termux but it fails to work without --softAes
-
cohcho
I need correct static build for aarch64 to test with hardware aes
-
tevador
it crashes without softAes?
-
cohcho
263ms per hash without largepages, without hardware aes
-
cohcho
No crash, your c++ code detects exception and prints 'try ... --softAes'
-
cohcho
without dataset *
-
tevador
what cmake options did you use?
-
tevador
it looks like AES code was not even compiled
-
cohcho
( No need to investigate it since termux environment is a shit )
-
tevador
you have to use just "cmake .." without ARCH to get the full build
-
tevador
native can exclude AES if it's wrongly detected
-
tevador
another option is that the compiler doesn't support it
-
tevador
-
tevador
you can try to comment out othe #ifdef and see what happens
-
cohcho
cross-compiled binary said 'Bad system call' via stderr within termux
-
cohcho
Can't find any rwx place to upload it via 'adb push'
-
cohcho
and test outside of termux
-
cohcho
It's likely that cross-compile environment with 5.x kernel isn't compatible with 4.x android kernel