02:42:11 <gingeropolous> lol... no worries.
18:48:03 <cohcho> Is it possible to launch 64-bit termux within 32-bit Android?
19:13:40 <sech1> Is it possible to launch any 64-bit app on 32-bit Android?
19:16:41 <cohcho> cpu should be 64-bit here
19:17:18 <cohcho> I suppose that user space binary can use 64-bit asm
19:23:30 <sech1> There's AArch64 execution state and AArch32 execution state. 64-bit state can run 32-bit code, but not the other way.
19:24:42 <sech1> https://community.arm.com/cfs-file/__key/communityserver-discussions-components-files/10/mixing_5F00_AArch32_5F00_and_5F00_AArch64.png
19:26:49 <cohcho> I've tried to find simple asm source to compile and test on the phone.
19:27:07 <cohcho> It would be some kind of runtime check
19:27:14 <cohcho> aarch64 specific asm *
19:27:20 <cohcho> But didn't find anything
19:51:39 <tevador> aarch32 OS cannot host an aarch64 userspace application
19:54:52 <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
19:55:32 <cohcho> If you're right then I'll see any error
19:59:37 <tevador> install CPU-Z from the playstore and go to System Tab
20:00:12 <tevador> you'll see either aarch64 or armv7l
20:01:35 <cohcho> armv8l
20:01:53 <tevador> that's 64-bit
20:02:15 <cohcho> Therefore I'm continue my road to compile runtime test
20:02:28 <cohcho> it's likely not reliable test
20:04:01 <tevador> I take it back, it looks like the 32-bit mode is called armv8l sometimes
20:04:39 <tevador> should say aarch64 in 64-bit mode
20:13:03 <cohcho> Can you modify this source to add dummy aes instruction ? https://raw.githubusercontent.com/matja/asm-examples/master/aarch64/hello.aarch64.linux.syscall.gas.asm
20:13:17 <cohcho> the same way as you did in c++ to test hardware aes support in runtime?
20:13:29 <cohcho> because hello wrold without aes is running fine here
20:26:37 <cohcho> or even better just static randomx-benchmark build for aarch64
20:28:49 <cohcho> I've added 3 instructions from randomx-benchmark and it works fine: http://paste.debian.net/hidden/c0786122/
20:29:22 <cohcho> Unfortunately, there is no static randomx-benchmark for aarch64 on github
20:29:38 <cohcho> all runtime tests have passed
20:30:34 <tevador> good, so you have a 64-bit ARM chip with crypto extensions
20:31:00 <cohcho> but that android app says armv8l
20:31:09 <cohcho> and termux is a shitty enviroment
20:31:14 <cohcho> the same level as cygwin
20:31:35 <sech1> can't you just try to compile xmrig in termux?
20:31:39 <cohcho> I'm going to cross-compile for aarch64
20:31:46 <cohcho> xmrig didn't even compiled due to lack of some headers
20:32:00 <sech1> works on my android phone, but it's 64 bit
20:32:05 <cohcho> xmrig hasn't been compiled due to errors *
20:38:11 <tevador> randomx-benchmark won't compile?
20:38:51 <cohcho> I've compiled randomx-benchmark successfuly in termux but it fails to work without --softAes
20:39:09 <cohcho> I need correct static build for aarch64 to test with hardware aes
20:39:20 <tevador> it crashes without softAes?
20:39:25 <cohcho> 263ms per hash without largepages, without hardware aes
20:39:41 <cohcho> No crash, your c++ code detects exception and prints 'try ... --softAes'
20:39:53 <cohcho> without dataset *
20:40:20 <tevador> what cmake options did you use?
20:40:52 <tevador> it looks like AES code was not even compiled
20:41:36 <cohcho> ( No need to investigate it since termux environment is a shit )
20:42:26 <tevador> you have to use just "cmake .." without ARCH to get the full build
20:42:41 <tevador> native can exclude AES if it's wrongly detected
20:43:07 <tevador> another option is that the compiler doesn't support it
20:44:35 <tevador> here: https://github.com/tevador/RandomX/blob/master/src/intrin_portable.h#L451
20:45:30 <tevador> you can try to comment out othe #ifdef and see what happens
20:57:54 <cohcho> cross-compiled binary said  'Bad system call' via stderr within termux
20:58:14 <cohcho> Can't find any rwx place to upload it via 'adb push'
20:58:24 <cohcho> and test outside of termux
21:12:01 <cohcho> It's likely that cross-compile environment with 5.x kernel isn't compatible with 4.x android kernel