Logue SDK on Visual Studio Code - cannot enable the ARM neon instrinsics

[fedemone]

Hi there,

I'm an happy owner of a Drumlogue, and I'm currently working on a potential yet ambitious project (on the sparse free time I have, so it means that I'm really slow), which is the porting of a open source physical modelling plug-in called RipplerX (it's free + open and you can find that on github, I already contacted the owner and I had his explicit permission) on the ARM Neon environment of the Logue SDK.
That should make the drumlogue a completely new instrument, as it shall reproduce different instruments and model with a lot of customizable parameters.

I'm accustomed to C++ SW programming (I know some Assembler stuff, too) and I'm using Visual Studio Code on my personal laptop (Windows11) instead of the professional one that I use for work, but I'm not able to make the Neon Intrinsics visible to the CLang that's running on VSC.
VSC extensions are the C++ developments tool (with the CMake pakages), as well the ARM development ones. I have LLVM installed, git, WSL and other basic tools.
I put the various includes in the settings.json of the VSC, I filled the tasks.json with the command (especially with -march=armv7-a -mtune=cortex-a7 -marm -Os -flto -mfloat-abi=hard -mfpu=neon-vfpv4 part that's crucial for the ARM defines), I spent hours among documentation and stakoverflow discussions about setting up clang for ARM (including some manual defines) but yet I'm not able to make the e.g. float32_t types visible by the IDE, as

#ifndef __ARM_FP #error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softp or -mfloat-abi=hard" #else

In the menatime I still work to the code, trying to exploit the vector intrinsics (I'm still studying those though) and to do some mathematical refactoring for some unoptimized code, but I really need to have VSC fully operational for finalizing this.

Currently the code is only local, but I'll be happy to share if anybody is interested in this. Please adive if you can.

Thanks in advance

[dukesrg]

Most probably you are overcomplicationg things.

1. Clone the repo
2. Add #include <arm_neon.h> to unit.cc of dummy.synth
3. Add some intrinsics in the code
4. Try to buld

I only wokred with SDK2.0 on MacOS though, so can't say how it works on W11.

[fedemone]

Thanks for the reply, my problem in this very moment is strictly with VSC, as it should help with syntax, variable scope, suggestions and other stuff an IDE is made for, since this porting is far more difficult than evaluated at first glance.
The file arm_neon.h is visible, but clang says are missing the defines that should be present when -mfloat-abi=hard is used, which is present in task.json.
Well, I'm still investigating and I'll put the project on GitHub for anybody interested into, any other comment or suggestion is highly welcome.

[dukesrg]

Do yo mean like here - VSCode underlines while the context help works, definitilon links to arm_neon.h works and code actually can be build with no issues?

[fedemone]

Yes, after some struggling with scripts for compiling (as said my paths using WSL are not as expected) I can confirm I can compile for drumlogue/dummy-synth

>> Building /workspace/drumlogue/dummy-synth
Compiling header.c
Compiling _unit_base.c
Compiling unit.cc

Linking build/dummy_synth.drmlgunit
Stripping build/dummy_synth.drmlgunit
Creating build/dummy_synth.hex
Creating build/dummy_synth.bin
Creating build/dummy_synth.dmp
Creating build/dummy_synth.list


Done

   text    data     bss     dec     hex filename
   3267     316       8    3591     e07 build/dummy_synth.drmlgunit
>> Installing /workspace/drumlogue/dummy-synth
Deploying to /workspace/drumlogue/dummy-synth//dummy_synth.drmlgunit

Done

>> Resetting environment
[drumlogue] ~ $

And after additional effort I finally made the VSC able to see correctly the toolchain, and intrinsics are not marked with squiggles (yes, as in your picture Oleg) by VSCode anymore!

Here's a screeshot, for example:

I can continue the porting (and the github project too... ). Thanks for the moment!

[fedemone]

If anybody interested, here my branch; still working on develop one until I try/succeed to compile. I'm really slow, I know, but stubborn:
https://github.com/fedemone/logue-sdk/tree/develop