Hi all,
I tried to compile "pc" using SSE3 instruction in order to run it on Core2 processor. The results of the test run do not seem exciting:
Actually, it looks that the version of pc provided by Tn-grid, although it only supports SSE2, runs like the version I compiled for SSE3 using
I take the occasion to ask someone more experienced than me if it is easy to compile pc for Android-x86_64 and Android-arm. I would like to do it and of course I would give the binary to anyone if I succeed. I compiled the android toolchain from the boinc package but then I do not know in which way should I modify the "make" file in the pc-boinc source to point to the android libraries and compiler instead of the standard g++ compiler. Sorry for my confusion but I am not a programmer, I just wanted to make a tentative in order to crunch Tn-grid's WUs on Android devices too. Considered that it looks like a very easy task for someone who know how to do it: is there any volunteer who wants to compile tn-grid for Android instead of me? Or perhaps suggesting me the needed steps? I think it could be of great value for the whole community!
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 623
Credit: 34,677,535
RAC: 9
The optimized versions (SSE2, AVX, FMA) of the application were built not only by giving the right directives to the compiler but also by writing some specific assembly code. Nevertheless the obtained speed gain was relatively small. The dramatic speed increase relative to the first version was mainly obtained by cleverly rewriting the source code. It seems to me that, because of the 'intrinsic' nature of our code, SIMD optimizations are not *very* useful.
Having a Android version of the application would be really fine. The application uses little RAM so it should fit, but I'm completely ignorant about Android development....
Reply
Quote
Ok so regarding the SIMD optimization I'll remain stick to the package provided by the server. It's fine as long as I am using my (slow) cpu efficiently.
Regarding Android, I think it is very easy for anyone with a clue on programming. I'm a complete newbie and nonetheless I was close to success only by following the official guide. I compiled the android_tc and and boinc libraries only by copying the commands. The problem was with the final step, that is, compiling "pc". I stopped just because the script provided by Boinc assumes that your app has a configure script, while "pc" has only a script that calls g++ and make and I do not know how to fix this, but just because I am ignorant: I recognize that it just matter of typing the right commands (calling the c++ compiler from the android toolchain) ;)
I can work on that by studying the procedure, but if you want take a look at it before I spend time just learning the basics.
This is the script:
all the files called by the script are created by other scripts included in the directory.[/code]
Reply
Quote
Eventually, we can try to compile it together? I have some expiriance with BOINC and BOINC science project porting to several platforms. But no Android device available and also less expiriance with Android.
I stopped just because the script provided by Boinc assumes that your app has a configure script, while "pc" has only a script that calls g++ and make and I do not know how to fix this, but just because I am ignorant: I recognize that it just matter of typing the right commands (calling the c++ compiler from the android toolchain) ;)
Am I understood you right, that you was able to comile the BOINC API and Library and the liniking of the "pc" binary produce errors?
For the macOS application, I have copied it to boinc/samples/tngrid, compiled it there.
On errors on the link stage (in the tngrid direcetroy), can you please issue a "gmake -n" to see the command which be issued for the linking of "pc".
Reply
Quote
I built Android apps in the past, here is link to my post with more details: http://gene.disi.unitn.it/test/forum_thread.php?id=158&postid=905#905
I did this by taking crosscompiler from Android NDK and connected it to existing Makefiles used for building project app. I found these makefles. Here are important parts of them:
From Makefile for 32-bit Android app:
From Makefile for 64-bit Android app:
I used these Makefiles from Cygwin. I hope that this will help you.
In Makefile for 32-bit app I has to use -mfloat-abi=softfp instead of -mfloat-abi=hard. This was required by Android. You can check if is is possible now, otherwise app will be slower than corresponding ARM Linux app.
____________
Reply
Quote
Thank you for your hints, Daniel.
I tried to go further in the compilation. Please keep in mind that I am an absolute beginner in the field so it is possible that I am doing silly mistakes.
What I've done:
1) Downloaded the android-r21 ndk. I think they changed something from the older version, in particular the compiler binary;
2) Compiled boinc for android-arm using the scripts provided in the source tree. The script compiled also an android toolkit (android-tc) and everything went smooth (and very fast despite I am using just a Core2Duo laptop)
3) I modified the Makefile present in PC-IM source tree using your suggestion:
Unfortunately, this does not work because it misses a "config.h" file needed by "parse.h":
This is weird because I am using the official source tree of boinc and it should be error free.
Daniel, do you still have the binary you compiled? Perhaps they are still valuable and we don't have to re-do the work again ;) They are no longer present in the archived you linked in your old post.
Reply
Quote
double post
Reply
Quote
Yes, this is known issue in BOINC. You need to manually copy config.h file from boinc source root dir to InstallPath/include/boinc after installing all files. Or if you use files from directly from boinc build dir, add /home/matteo/Software/boinc/ to include paths.
You can also modify this parse.h to use #include "../config.h".
____________
Reply
Quote
I tried all day, but I am not able to do it. Now I receive
I give up the idea, I hope that someone more experienced than me may do it.
In case, my only suggestion is to build for all the possible platforms: once you are able to compile it's a matter of minutes to compile for several platforms, and it would be an added value to tn-grid. For example, in this moment no projects are able to run on android-x86. [/code]
Reply
Quote
The optimized versions (SSE2, AVX, FMA) of the application ...
Somewhat off-topic, but are there any plans to add Windows FMA app?
It would not impact my computer, but at least some of those Windows machines currently running AVX app should be able to benefit, right?
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 623
Credit: 34,677,535
RAC: 9
The optimized versions (SSE2, AVX, FMA) of the application ...
Somewhat off-topic, but are there any plans to add Windows FMA app?
It would not impact my computer, but at least some of those Windows machines currently running AVX app should be able to benefit, right?
We had problems with v1.10 Windows FMA version (mainly for AMD cpus, early bioses) so we decided not to build it when switching to v1.11, also the speed increase was minimal (in some cases the AVX version performed better). I may try to rebuild it and put it on beta, have to think about it.
Reply
Quote
Hi!
I'm try to compile an Android binary but I have this error when manually build TN-Grid executable
This is my build script https://bin.disroot.org/?efa76485d88e614e#2uMR2WgifRtYuFyW8vEfHdEU56N5NYDnz87wsk4sQTzd
And my app Makefile https://bin.disroot.org/?7ab51c427cb1f791#BqdC6EUshq1wLLWEKHp3UW4hz6tzsCirxxmP68t3Vt8C
[/url]
____________
Consulta como ver TV y leer noticias desde tu movil en una sola app con FeedTV.
Apoya la investigación desde esta imagen
Reply
Quote
It looks that bzip2 library was build with -D_FORTIFY_SOURCE, which is not supported by glibc on Android. You need to rebuild bzip2 with this flag disabled. Here is related question on StackOverflow:
https://stackoverflow.com/questions/22977898/android-4-4-undefined-reference-to-printf-chk
____________
Reply
Quote
It looks that bzip2 library was build with -D_FORTIFY_SOURCE, which is not supported by glibc on Android. You need to rebuild bzip2 with this flag disabled. Here is related question on StackOverflow:
https://stackoverflow.com/questions/22977898/android-4-4-undefined-reference-to-printf-chk
Thanks, I build bzip2 and make with compiled lib and work fine!!
Now, how can I test this binary to view that ir work fine?
____________
Consulta como ver TV y leer noticias desde tu movil en una sola app con FeedTV.
Apoya la investigación desde esta imagen
Reply
Quote
You have to put in the project's director an app_info.xml file with the name of your executable and then restart boinc.
https://boinc.berkeley.edu/wiki/Anonymous_platform
let us know if everything goes fine!
Then, if your procedure worked, you could explain all the passage you've done so that we will be able to compile also for arm32.
Did you compile the app with some extension? (ex. NEON, PIE)
Reply
Quote
You have to put in the project's director an app_info.xml file with the name of your executable and then restart boinc.
https://boinc.berkeley.edu/wiki/Anonymous_platform
let us know if everything goes fine!
Then, if your procedure worked, you could explain all the passage you've done so that we will be able to compile also for arm32.
Did you compile the app with some extension? (ex. NEON, PIE)
Thanks! I try this and for the moment it works fine!!
Definitive build script android64_build.sh https://bin.disroot.org/?cae7d50e268c2abd#4VXpES87gfvQFgW7QkHnCG5fyCTumuKC3hMYofNGPY2R
Definitive makefile https://bin.disroot.org/?81265057234777a3#9tJmVrkUwAWRc5dVyrFQf49LRj5sWDcwo4nZAV8pYZK8 (optimiced for cortex a53, you can change for other -mtune value defined in https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/AArch64-Options.html#aarch64-feature-modifiers)
I try this steps:
Clone https://github.com/truboxl/boinc-android
Run 00_prepare_sources.sh to download necesary files (boinc, android ndk...)
Clone https://bitbucket.org/francesco-asnicar/pc-boinc/src/master/ in /boinc-android/src/boinc/samples
copy /boinc-android/src/boinc/android/build_boinc_arm64.sh to /boinc-android/src/boinc/samples/pc-boinc/src/android64_build.sh
Edit android64_build.sh to add --disable-client in configure, make pc-im...
Edit makefile to add ARCH, toolchains and some Android flags
____________
Consulta como ver TV y leer noticias desde tu movil en una sola app con FeedTV.
Apoya la investigación desde esta imagen
Reply
Quote
You have to put in the project's director an app_info.xml file with the name of your executable and then restart boinc.
https://boinc.berkeley.edu/wiki/Anonymous_platform
let us know if everything goes fine!
Then, if your procedure worked, you could explain all the passage you've done so that we will be able to compile also for arm32.
Did you compile the app with some extension? (ex. NEON, PIE)
AARCH64 apps for Android always are PIE and have NEON enabled.
____________
Reply
Quote
Hi all!
now, I sucessfully compile a 32 bits armv7-a version
I will try to test if it works well on my Ifive mini 4. http://gene.disi.unitn.it/test/show_host_detail.php?hostid=58688
Definitive build script android32_build.sh https://bin.disroot.org/?8a895f9191fe1cdd#AN1MyMVoqv2t7x9dKQ4z7VHYVCvj4LEe44uggQ1PzZqU
Definitive makefile https://bin.disroot.org/?981945d91a0f2297#4VCRaZHSEQei5DNYjWAccQ97AiGkxbevXed82dxxyeHu (optimiced for cortex a17, with neon-vfpv4, you can change for other -mtune value defined in https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/ARM-Options.html#ARM-Options)
Regarding the 64-bit version, at the moment it works well on my Huawei Nova with boinc in termux http://gene.disi.unitn.it/test/show_host_detail.php?hostid=58688
____________
Consulta como ver TV y leer noticias desde tu movil en una sola app con FeedTV.
Apoya la investigación desde esta imagen
Reply
Quote
Hi,
I have compiled an optimized version of the app for my cpu, an Intel Xeon L5420. I got a good increase in performance: the running time passed from an average of 25500 seconds to 19500.
I have used these flags for GCC:
I compiled the application twice:
first time I used -fprofile-generated and ran the application for a while; it generated some .gcda files in the src directory: these files are profile files that enable to further optimize the binary, in order to have it very tailored to your system.
So the second step was to use -fprofile-use in order to use the gcda files previously generated. Actually I didn't created very good profile files, I just ran four or five times the very rapid tests included in the source tree.
I'd like to share this binary with you: https://drive.google.com/file/d/1nGfHSGxbS3QXKp8dIPIqGh5HyJLeRn4g/view?usp=sharing
I have seen several hosts using cpu similar to mine on this project, so other users could use it to increase credit and science ;)
Reply
Quote
Nice,
Hope it can be brought to the official app list.
____________
Reply
Quote