pffft and NTC C.H.I.P (was Re: [Csnd] pffft.c and Raspberry Pi 3)

Date	2016-06-02 19:44
From	Anders Genell
Subject	pffft and NTC C.H.I.P (was Re: [Csnd] pffft.c and Raspberry Pi 3)
	Ok, I'll skip the ticket for now and just fork a separate thread here. So, info about the little gadget can most easily be found at www.getchip.com As a start I'll post gcc -v and cpuinfo below: chip@chip:~$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/ Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversio/usr/share/doc/gcc-4.9/README.Bugs --enable-languagesrefix=/usr --program-suffix=-4.9 --enable-shared --enb --without-included-gettext --enable-threads=posix -9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --eg --enable-libstdcxx-time=yes --enable-gnu-unique-objh --enable-plugin --with-system-zlib --disable-browsetk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcjjvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --a-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --wit --enable-objc-gc --enable-multiarch --disable-sjlj-evfpv3-d16 --with-float=hard --with-mode=thumb --enablabihf --host=arm-linux-gnueabihf --target=arm-linux-g Thread model: posix gcc version 4.9.2 (Debian 4.9.2-10) cat /proc/cpu cpu/ cpuinfo chip@chip:~$ cat /proc/cpu/ alignment swp_emulation chip@chip:~$ cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 2 (v7l) BogoMIPS : 1001.88 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part : 0xc08 CPU revision : 2 Hardware : Allwinner sun4i/sun5i Families Revision : 0000 Serial : 1625425303409075 I'll follow up with errors from attempted builds in a separate email. I could open a ssh-port to the machine if someone wants to play around with it. Regards, Anders > 2 juni 2016 kl. 20:31 skrev Victor Lazzarini : > > Not sure it warrants an issue, but if you feel you'd like to open it, go ahead. > > Note that we can't build this because we do not have the hardware or cross-compiler. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 2 Jun 2016, at 18:22, Anders Genell wrote: >> >> Thanks! I'll try a little more to see what I can find. Maybe I should start a separate thread/ticket to keep this from obfuscating the OP's (solved) issue? >> >> Regards, >> Anders >> >>> 2 juni 2016 kl. 18:02 skrev Victor Lazzarini : >>> >>> The neon extensions are defined by an API that I think is common to all hardware that implement it. >>> Did you try just adding -mfpu=neon to see what happens (leaving the other flag)? Also why is ‘hard’ not compiling, >>> what errors are you getting? >>> >>> Otherwise, you will need to try and look it up on the interweb, see for instance >>> >>> https://www.raspberrypi.org/forums/viewtopic.php?f=33&t=98354 >>> >>> It looks like it should be definitely possible. >>> ======================== >>> Dr Victor Lazzarini >>> Dean of Arts, Celtic Studies and Philosophy, >>> Maynooth University, >>> Maynooth, Co Kildare, Ireland >>> Tel: 00 353 7086936 >>> Fax: 00 353 1 7086952 >>> >>>> On 2 Jun 2016, at 16:36, Anders Genell wrote: >>>> >>>> Ok, after trying a bit it seems I really cannot get it to work. >>>> >>>> The country info says it supports neon, but with mfloat-abi=hard compilation fails, and trying =softfp causes cmake not to find if the cpu is bigendian or not... >>>> >>>> Are there versions of neon, so that csound includes support for one but not another? >>>> >>>> Regards, >>>> Anders >>>> >>>>> 1 juni 2016 kl. 09:22 skrev Victor Lazzarini : >>>>> >>>>> Here are some pointers: >>>>> >>>>> 1. In the top level directory, there is an example Custom.cmake called Custom.cmake.ex, rename it Custom.cmake. >>>>> >>>>> 2. Open the file. You will see this line: >>>>> >>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -W -Wall -mtune=core2”) >>>>> >>>>> This is where the C compiler flags can be set. Change it to something like >>>>> >>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mfloat-abi=hard -mfpu=neon”) >>>>> >>>>> then build as usual >>>>> >>>>> If it builds OK, then the PFFFT lib will be using NEON. To use this library, add --fftlib=1 to the Csound options. >>>>> >>>>> Regards >>>>> ======================== >>>>> Dr Victor Lazzarini >>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>> Maynooth University, >>>>> Maynooth, Co Kildare, Ireland >>>>> Tel: 00 353 7086936 >>>>> Fax: 00 353 1 7086952 >>>>> >>>>>> On 31 May 2016, at 20:00, Anders Genell wrote: >>>>>> >>>>>> ...and what should custom.cmake look like to enable neon? And where should it be? In my build dir? >>>>>> >>>>>> Regards, >>>>>> Anders >>>>>> >>>>>>> 31 maj 2016 kl. 20:28 skrev Anders Genell : >>>>>>> >>>>>>> Hm. I'm likely out of my depth here... >>>>>>> The cpu seems neon capable: >>>>>>> >>>>>>> chip@chip:~/Src/csound/csound6$ cat /proc/cpuinfo >>>>>>> processor : 0 >>>>>>> model name : ARMv7 Processor rev 2 (v7l) >>>>>>> BogoMIPS : 1001.88 >>>>>>> Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 >>>>>>> CPU implementer : 0x41 >>>>>>> CPU architecture: 7 >>>>>>> CPU variant : 0x3 >>>>>>> CPU part : 0xc08 >>>>>>> CPU revision : 2 >>>>>>> >>>>>>> Hardware : Allwinner sun4i/sun5i Families >>>>>>> Revision : 0000 >>>>>>> >>>>>>> How do I make sure the tool chain has neon support? >>>>>>> >>>>>>> Regards, >>>>>>> Anders >>>>>>> >>>>>>>> 31 maj 2016 kl. 13:29 skrev Victor Lazzarini : >>>>>>>> >>>>>>>> yes, you can try adding these flags, but to custom.cmake, not CMakeCache.txt, >>>>>>>> The toolchain needs to support it, though, but you will know if it doesn’t because it will not compile. >>>>>>>> >>>>>>>> ======================== >>>>>>>> Dr Victor Lazzarini >>>>>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>>>>> Maynooth University, >>>>>>>> Maynooth, Co Kildare, Ireland >>>>>>>> Tel: 00 353 7086936 >>>>>>>> Fax: 00 353 1 7086952 >>>>>>>> >>>>>>>>> On 31 May 2016, at 10:06, Anders Genell wrote: >>>>>>>>> >>>>>>>>> I just tried to build on a NextThingCo CHIP (ARM R8) and had the same issue. It seems the CHIP should have NEON support - should I then NOT add the flags to CMakeCache.txt, but add -mfloat-abi=hard mfpu=neon to the make command? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Anders >>>>>>>>> >>>>>>>>>> 26 maj 2016 kl. 14:34 skrev ebmtranceboy : >>>>>>>>>> >>>>>>>>>> Ok I can compile with -mfloat-abi=hard -mfpu=neon but not with -mfloat-abi=softfp (I added this to BUILD.md). >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-06-02 21:00
From	Victor Lazzarini
Subject	Re: pffft and NTC C.H.I.P (was Re: [Csnd] pffft.c and Raspberry Pi 3)
	If there is a ssh way into it, I can give it a go at some point. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 2 Jun 2016, at 19:44, Anders Genell wrote: > > Ok, I'll skip the ticket for now and just fork a separate thread here. > > So, info about the little gadget can most easily be found at www.getchip.com > > As a start I'll post gcc -v and cpuinfo below: > > chip@chip:~$ gcc -v > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/ > Target: arm-linux-gnueabihf > Configured with: ../src/configure -v --with-pkgversio/usr/share/doc/gcc-4.9/README.Bugs --enable-languagesrefix=/usr --program-suffix=-4.9 --enable-shared --enb --without-included-gettext --enable-threads=posix -9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --eg --enable-libstdcxx-time=yes --enable-gnu-unique-objh --enable-plugin --with-system-zlib --disable-browsetk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcjjvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --a-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --wit --enable-objc-gc --enable-multiarch --disable-sjlj-evfpv3-d16 --with-float=hard --with-mode=thumb --enablabihf --host=arm-linux-gnueabihf --target=arm-linux-g > Thread model: posix > gcc version 4.9.2 (Debian 4.9.2-10) > > cat /proc/cpu > cpu/ cpuinfo > chip@chip:~$ cat /proc/cpu/ > alignment swp_emulation > chip@chip:~$ cat /proc/cpuinfo > processor : 0 > model name : ARMv7 Processor rev 2 (v7l) > BogoMIPS : 1001.88 > Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 > CPU implementer : 0x41 > CPU architecture: 7 > CPU variant : 0x3 > CPU part : 0xc08 > CPU revision : 2 > > Hardware : Allwinner sun4i/sun5i Families > Revision : 0000 > Serial : 1625425303409075 > > > I'll follow up with errors from attempted builds in a separate email. > I could open a ssh-port to the machine if someone wants to play around with it. > > Regards, > Anders > >> 2 juni 2016 kl. 20:31 skrev Victor Lazzarini : >> >> Not sure it warrants an issue, but if you feel you'd like to open it, go ahead. >> >> Note that we can't build this because we do not have the hardware or cross-compiler. >> >> Victor Lazzarini >> Dean of Arts, Celtic Studies, and Philosophy >> Maynooth University >> Ireland >> >>> On 2 Jun 2016, at 18:22, Anders Genell wrote: >>> >>> Thanks! I'll try a little more to see what I can find. Maybe I should start a separate thread/ticket to keep this from obfuscating the OP's (solved) issue? >>> >>> Regards, >>> Anders >>> >>>> 2 juni 2016 kl. 18:02 skrev Victor Lazzarini : >>>> >>>> The neon extensions are defined by an API that I think is common to all hardware that implement it. >>>> Did you try just adding -mfpu=neon to see what happens (leaving the other flag)? Also why is ‘hard’ not compiling, >>>> what errors are you getting? >>>> >>>> Otherwise, you will need to try and look it up on the interweb, see for instance >>>> >>>> https://www.raspberrypi.org/forums/viewtopic.php?f=33&t=98354 >>>> >>>> It looks like it should be definitely possible. >>>> ======================== >>>> Dr Victor Lazzarini >>>> Dean of Arts, Celtic Studies and Philosophy, >>>> Maynooth University, >>>> Maynooth, Co Kildare, Ireland >>>> Tel: 00 353 7086936 >>>> Fax: 00 353 1 7086952 >>>> >>>>> On 2 Jun 2016, at 16:36, Anders Genell wrote: >>>>> >>>>> Ok, after trying a bit it seems I really cannot get it to work. >>>>> >>>>> The country info says it supports neon, but with mfloat-abi=hard compilation fails, and trying =softfp causes cmake not to find if the cpu is bigendian or not... >>>>> >>>>> Are there versions of neon, so that csound includes support for one but not another? >>>>> >>>>> Regards, >>>>> Anders >>>>> >>>>>> 1 juni 2016 kl. 09:22 skrev Victor Lazzarini : >>>>>> >>>>>> Here are some pointers: >>>>>> >>>>>> 1. In the top level directory, there is an example Custom.cmake called Custom.cmake.ex, rename it Custom.cmake. >>>>>> >>>>>> 2. Open the file. You will see this line: >>>>>> >>>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -W -Wall -mtune=core2”) >>>>>> >>>>>> This is where the C compiler flags can be set. Change it to something like >>>>>> >>>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mfloat-abi=hard -mfpu=neon”) >>>>>> >>>>>> then build as usual >>>>>> >>>>>> If it builds OK, then the PFFFT lib will be using NEON. To use this library, add --fftlib=1 to the Csound options. >>>>>> >>>>>> Regards >>>>>> ======================== >>>>>> Dr Victor Lazzarini >>>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>>> Maynooth University, >>>>>> Maynooth, Co Kildare, Ireland >>>>>> Tel: 00 353 7086936 >>>>>> Fax: 00 353 1 7086952 >>>>>> >>>>>>> On 31 May 2016, at 20:00, Anders Genell wrote: >>>>>>> >>>>>>> ...and what should custom.cmake look like to enable neon? And where should it be? In my build dir? >>>>>>> >>>>>>> Regards, >>>>>>> Anders >>>>>>> >>>>>>>> 31 maj 2016 kl. 20:28 skrev Anders Genell : >>>>>>>> >>>>>>>> Hm. I'm likely out of my depth here... >>>>>>>> The cpu seems neon capable: >>>>>>>> >>>>>>>> chip@chip:~/Src/csound/csound6$ cat /proc/cpuinfo >>>>>>>> processor : 0 >>>>>>>> model name : ARMv7 Processor rev 2 (v7l) >>>>>>>> BogoMIPS : 1001.88 >>>>>>>> Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 >>>>>>>> CPU implementer : 0x41 >>>>>>>> CPU architecture: 7 >>>>>>>> CPU variant : 0x3 >>>>>>>> CPU part : 0xc08 >>>>>>>> CPU revision : 2 >>>>>>>> >>>>>>>> Hardware : Allwinner sun4i/sun5i Families >>>>>>>> Revision : 0000 >>>>>>>> >>>>>>>> How do I make sure the tool chain has neon support? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Anders >>>>>>>> >>>>>>>>> 31 maj 2016 kl. 13:29 skrev Victor Lazzarini : >>>>>>>>> >>>>>>>>> yes, you can try adding these flags, but to custom.cmake, not CMakeCache.txt, >>>>>>>>> The toolchain needs to support it, though, but you will know if it doesn’t because it will not compile. >>>>>>>>> >>>>>>>>> ======================== >>>>>>>>> Dr Victor Lazzarini >>>>>>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>>>>>> Maynooth University, >>>>>>>>> Maynooth, Co Kildare, Ireland >>>>>>>>> Tel: 00 353 7086936 >>>>>>>>> Fax: 00 353 1 7086952 >>>>>>>>> >>>>>>>>>> On 31 May 2016, at 10:06, Anders Genell wrote: >>>>>>>>>> >>>>>>>>>> I just tried to build on a NextThingCo CHIP (ARM R8) and had the same issue. It seems the CHIP should have NEON support - should I then NOT add the flags to CMakeCache.txt, but add -mfloat-abi=hard mfpu=neon to the make command? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Anders >>>>>>>>>> >>>>>>>>>>> 26 maj 2016 kl. 14:34 skrev ebmtranceboy : >>>>>>>>>>> >>>>>>>>>>> Ok I can compile with -mfloat-abi=hard -mfpu=neon but not with -mfloat-abi=softfp (I added this to BUILD.md). >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-06-02 21:03
From	Anders Genell
Subject	Re: pffft and NTC C.H.I.P (was Re: [Csnd] pffft.c and Raspberry Pi 3)
	Brilliant! I'll email you off list. Regards, Anders > 2 juni 2016 kl. 22:00 skrev Victor Lazzarini : > > If there is a ssh way into it, I can give it a go at some point. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 2 Jun 2016, at 19:44, Anders Genell wrote: >> >> Ok, I'll skip the ticket for now and just fork a separate thread here. >> >> So, info about the little gadget can most easily be found at www.getchip.com >> >> As a start I'll post gcc -v and cpuinfo below: >> >> chip@chip:~$ gcc -v >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/ >> Target: arm-linux-gnueabihf >> Configured with: ../src/configure -v --with-pkgversio/usr/share/doc/gcc-4.9/README.Bugs --enable-languagesrefix=/usr --program-suffix=-4.9 --enable-shared --enb --without-included-gettext --enable-threads=posix -9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --eg --enable-libstdcxx-time=yes --enable-gnu-unique-objh --enable-plugin --with-system-zlib --disable-browsetk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcjjvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --a-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --wit --enable-objc-gc --enable-multiarch --disable-sjlj-evfpv3-d16 --with-float=hard --with-mode=thumb --enablabihf --host=arm-linux-gnueabihf --target=arm-linux-g >> Thread model: posix >> gcc version 4.9.2 (Debian 4.9.2-10) >> >> cat /proc/cpu >> cpu/ cpuinfo >> chip@chip:~$ cat /proc/cpu/ >> alignment swp_emulation >> chip@chip:~$ cat /proc/cpuinfo >> processor : 0 >> model name : ARMv7 Processor rev 2 (v7l) >> BogoMIPS : 1001.88 >> Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 >> CPU implementer : 0x41 >> CPU architecture: 7 >> CPU variant : 0x3 >> CPU part : 0xc08 >> CPU revision : 2 >> >> Hardware : Allwinner sun4i/sun5i Families >> Revision : 0000 >> Serial : 1625425303409075 >> >> >> I'll follow up with errors from attempted builds in a separate email. >> I could open a ssh-port to the machine if someone wants to play around with it. >> >> Regards, >> Anders >> >>> 2 juni 2016 kl. 20:31 skrev Victor Lazzarini : >>> >>> Not sure it warrants an issue, but if you feel you'd like to open it, go ahead. >>> >>> Note that we can't build this because we do not have the hardware or cross-compiler. >>> >>> Victor Lazzarini >>> Dean of Arts, Celtic Studies, and Philosophy >>> Maynooth University >>> Ireland >>> >>>> On 2 Jun 2016, at 18:22, Anders Genell wrote: >>>> >>>> Thanks! I'll try a little more to see what I can find. Maybe I should start a separate thread/ticket to keep this from obfuscating the OP's (solved) issue? >>>> >>>> Regards, >>>> Anders >>>> >>>>> 2 juni 2016 kl. 18:02 skrev Victor Lazzarini : >>>>> >>>>> The neon extensions are defined by an API that I think is common to all hardware that implement it. >>>>> Did you try just adding -mfpu=neon to see what happens (leaving the other flag)? Also why is ‘hard’ not compiling, >>>>> what errors are you getting? >>>>> >>>>> Otherwise, you will need to try and look it up on the interweb, see for instance >>>>> >>>>> https://www.raspberrypi.org/forums/viewtopic.php?f=33&t=98354 >>>>> >>>>> It looks like it should be definitely possible. >>>>> ======================== >>>>> Dr Victor Lazzarini >>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>> Maynooth University, >>>>> Maynooth, Co Kildare, Ireland >>>>> Tel: 00 353 7086936 >>>>> Fax: 00 353 1 7086952 >>>>> >>>>>> On 2 Jun 2016, at 16:36, Anders Genell wrote: >>>>>> >>>>>> Ok, after trying a bit it seems I really cannot get it to work. >>>>>> >>>>>> The country info says it supports neon, but with mfloat-abi=hard compilation fails, and trying =softfp causes cmake not to find if the cpu is bigendian or not... >>>>>> >>>>>> Are there versions of neon, so that csound includes support for one but not another? >>>>>> >>>>>> Regards, >>>>>> Anders >>>>>> >>>>>>> 1 juni 2016 kl. 09:22 skrev Victor Lazzarini : >>>>>>> >>>>>>> Here are some pointers: >>>>>>> >>>>>>> 1. In the top level directory, there is an example Custom.cmake called Custom.cmake.ex, rename it Custom.cmake. >>>>>>> >>>>>>> 2. Open the file. You will see this line: >>>>>>> >>>>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -W -Wall -mtune=core2”) >>>>>>> >>>>>>> This is where the C compiler flags can be set. Change it to something like >>>>>>> >>>>>>> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mfloat-abi=hard -mfpu=neon”) >>>>>>> >>>>>>> then build as usual >>>>>>> >>>>>>> If it builds OK, then the PFFFT lib will be using NEON. To use this library, add --fftlib=1 to the Csound options. >>>>>>> >>>>>>> Regards >>>>>>> ======================== >>>>>>> Dr Victor Lazzarini >>>>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>>>> Maynooth University, >>>>>>> Maynooth, Co Kildare, Ireland >>>>>>> Tel: 00 353 7086936 >>>>>>> Fax: 00 353 1 7086952 >>>>>>> >>>>>>>> On 31 May 2016, at 20:00, Anders Genell wrote: >>>>>>>> >>>>>>>> ...and what should custom.cmake look like to enable neon? And where should it be? In my build dir? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Anders >>>>>>>> >>>>>>>>> 31 maj 2016 kl. 20:28 skrev Anders Genell : >>>>>>>>> >>>>>>>>> Hm. I'm likely out of my depth here... >>>>>>>>> The cpu seems neon capable: >>>>>>>>> >>>>>>>>> chip@chip:~/Src/csound/csound6$ cat /proc/cpuinfo >>>>>>>>> processor : 0 >>>>>>>>> model name : ARMv7 Processor rev 2 (v7l) >>>>>>>>> BogoMIPS : 1001.88 >>>>>>>>> Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 >>>>>>>>> CPU implementer : 0x41 >>>>>>>>> CPU architecture: 7 >>>>>>>>> CPU variant : 0x3 >>>>>>>>> CPU part : 0xc08 >>>>>>>>> CPU revision : 2 >>>>>>>>> >>>>>>>>> Hardware : Allwinner sun4i/sun5i Families >>>>>>>>> Revision : 0000 >>>>>>>>> >>>>>>>>> How do I make sure the tool chain has neon support? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Anders >>>>>>>>> >>>>>>>>>> 31 maj 2016 kl. 13:29 skrev Victor Lazzarini : >>>>>>>>>> >>>>>>>>>> yes, you can try adding these flags, but to custom.cmake, not CMakeCache.txt, >>>>>>>>>> The toolchain needs to support it, though, but you will know if it doesn’t because it will not compile. >>>>>>>>>> >>>>>>>>>> ======================== >>>>>>>>>> Dr Victor Lazzarini >>>>>>>>>> Dean of Arts, Celtic Studies and Philosophy, >>>>>>>>>> Maynooth University, >>>>>>>>>> Maynooth, Co Kildare, Ireland >>>>>>>>>> Tel: 00 353 7086936 >>>>>>>>>> Fax: 00 353 1 7086952 >>>>>>>>>> >>>>>>>>>>> On 31 May 2016, at 10:06, Anders Genell wrote: >>>>>>>>>>> >>>>>>>>>>> I just tried to build on a NextThingCo CHIP (ARM R8) and had the same issue. It seems the CHIP should have NEON support - should I then NOT add the flags to CMakeCache.txt, but add -mfloat-abi=hard mfpu=neon to the make command? >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Anders >>>>>>>>>>> >>>>>>>>>>>> 26 maj 2016 kl. 14:34 skrev ebmtranceboy : >>>>>>>>>>>> >>>>>>>>>>>> Ok I can compile with -mfloat-abi=hard -mfpu=neon but not with -mfloat-abi=softfp (I added this to BUILD.md). >>>>>>>>>>>> >>>>>>>>>>>> Csound mailing list >>>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>>> Send bugs reports to >>>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>>> >>>>>>>>>>> Csound mailing list >>>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>>> Send bugs reports to >>>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here