I have compiled the application for ARM devices running GNU/Linux (Raspberry Pi and co.)

Here are three versions and an app_info.xml to run them on boinc as Anonymous platform

vfp
vfpv3
vfpv4

app_info.xml


Keep the app that match fp unit of your device soc (for example vfp for classic armv6 raspberry, vfpv4 for new raspberry/banana/orange pi)
I found really poor (near nothing) performance gain among the three so you can just take the first and it will be good on all devices.

You need also the app_info.xml
The name of the application file have to match the name inside the app_info so rename it as "pc" only (or modify the app_info)

Attach your device to the project, copy both files in the directory (usually /var/lib/boinc-client/projects/gene.disi.unitn.it_test/ ) and make executable the file pc.
Restart boinc and it should start to get work from TN-Grid



If you want to test all the three there is a testing script on github with stuff provided by Francesco. Keep all the project:

Thank you for testing koschi.

The project source code is available as announced here.

I am thinking to take a 64 bit board, maybe an Odroid C2 or an Hikey and I'll try to compile but I really don't know if there will be any gain cause I'm not a programmer.
____________

I used some -m flags but they don't make much difference. See the build scripts in my repo
:
See also the Makefile, I added there the -fsigned-char flag. This is very important, without that the code don't works. I suspect this is your problem :)
____________

Yep thanks, shortly after posting, I stumbled over the thread and managed to compile the source. Unfortunately the test run times are in the 8-9min range. They tend to get worse specifying matching -march and -mtune for the C2's A53 cores.

I'm no programmer nor advanced compilation pro, so I leave it like this for now.

Did you change any cflags etc? The C2 has only very limited information in /proc/cpuinfo, maybe thats part of the problem, that it can't determine its capabilities and account for them during build...

I added right now an armv8 application. This should work in 64 bit only os.
I can't edit my first post, download here:

armv8
____________

Thanks a ton!

So far I only did the test_run.sh and replaced the binary on one system (no completed WUs yet). The benchmark looks very promising though, wow!

root@odroidc2-1:~/rpi-boinc-ap/pc-boinc# ./test_run.sh
Running test with bin/pcv7:

real 0m23.641s
user 0m21.550s
sys 0m0.100s
Running test with bin/pcv8:

real 0m10.500s
user 0m8.430s
sys 0m0.070s

edit:

the DL link was no longer valid, I used https://raw.githubusercontent.com/sorcrosc/rpi-boinc-ap/master/TN-Grid/bin/pc_armv8-a.tgz to get the v8 binary...

I'm replacing all versions with others based on your code, Daniel. Only the armv6 is missing now.
The armv8 koschi tested is already yours and seems also about 5% faster over armv7 on my device.
I also changed the test data with the Daniel's one (ec experiments) which show more realistic results.
____________

Here are all tarballs with new application based on Daniel optimized code and app_info included:

armv6
armv7_vfpv3
armv7_vfpv4
armv8

If you want to test the fastest one then install git and clone the repo:

I have just read that AARCH64 CPUs has new NEON SIMD instructions with double precision support, so it should be possible to get additional speed boost by using them. Probably it is time to get some Odroid C2 and play with it a bit :)
____________

I have just read that AARCH64 CPUs has new NEON SIMD instructions with double precision support, so it should be possible to get additional speed boost by using them. Probably it is time to get some Odroid C2 and play with it a bit :)