no neon?

[ab1jx]

The Rock64 doesn't do Neon?  That's a shock. I was trying to build cpuminer https://github.com/pooler/cpuminer

I have it built and running on 2 or 3 Rpi 3's then I turned to the Rock64.  I get the obnoxious message that the compiler cannot create executables, which can mean anything, there was just some error compiling a test program.

This doesn't work on my Rock64 (does on Pis)
./configure CFLAGS="-O3 -mfpu=neon"

If I drop out the neon part so it's just
./configure CFLAGS="-O3"

Then it works.  But you get just compiled C, not the ARM assembly language that Pooler wrote.  So it's slower than a Pi.  I get 0.97 khash/s instead of 1.32 or so.  (Per thread)

If I do cat /proc/cpuinfo that mentions neon on a Pi, not on a Rock64.

[ab1jx]

It's not that it doesn't have Neon, it's that the assembly code was written for 32-bit ARMs.  See https://github.com/pooler/cpuminer/issues/177  Should work fine for other programs.

[pas059]

Hi,
i use 64 bits ARMv8 with neon and this works on rokc64. As i remember 32 bits ARM neon assembly or intrinsics instructions are not recognised on rock64
regards

[ab1jx]

I can make it work but it's no faster than the compiled C, something on the order of 0.95 khash/s (per thread) which is about the same as a Raspberry Pi can do without the assembly.  On the Pi I can configure with
./configure CFLAGS="-O3 -mfpu=neon"
which uses the assembly and it speeds up to 1.17 - 1.3 khash/s

On aarch64 it's not valid to use the -mfpu=neon flag so the configure step fails.  The github link led me to https://stackoverflow.com/questions/2985...-mfpu-neon which led me to https://gcc.gnu.org/onlinedocs/gcc-4.8.2...64-Options

I spent most of an hour trying various options but never saw any speedup.  Cpuminer has (at this point) separate assembly language sections for arm, ppc, x64, x86, but not aarch64 which the Rock64 is.

I taught myself x86 assembly in the early 1990s but on an 8088 (8 bit) machine.  The register names are mostly different when you jump even to a 16 bit machine.  Somewhere it says that 32 bit arm is a whole different backend than aarch64.

I'd like to see a variation on cpuminer that ran a couple threads on the CPU and a couple on the GPU but that's far-fetched.  And an ASIC is about 1000 times faster anyway so it's pointless.

[pas059]

If I do cat /proc/cpuinfo that mentions neon on a Pi, not on a Rock64.

If I do cat /proc/cpuinfo on my Rock64 under Armbian, it mentions asimd, which is neon, i assume
Regards

[ab1jx]

Yes, I think so, I see "fp asimd evtstrm aes pmull sha1 sha2 crc32" from my Ayufan one. But the cpuminer configure script fails because it's looking for neon in a 32-bit context, plus it has handwritten (I think) assembly language code only for 32bit arm. It gives me the "compiler cannot create executables" error because the test program it tries to compile as part of the configure process chokes on the "-mfpu=neon" flag, since neon is built in with aarch64.