• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 844 views
  • Users 0 members are here
Support feedback
Options
Options

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NEON intrinsics CCS semantic errors.

Ilja Fursov
Prodigy 200 points

Dear CCS community,

I am working on linux user application for Sitara AM335x processors and I am using external compiler arm-linux-gnueabihf-gcc (Linaro GCC 4.9-2015.05) 4.9.3 20150413 which was provided with mainline linux sdk from TI.

I would like to involve NEON intrinsics. 

Here are copilation flags -O3 -time -g3 -Wall -c -mcpu=cortex-a8 -mfloat-abi=hard -mfpu=neon.

My code compiles but I still get semantic errors e.g. "Type int16x4_t could not be resolved".

Any ideas?

Best regards,

Ilja.

  • 0
    TI__Guru**** 169754 points
    Ilja,

    If your project is based on a makefile (and not a managed project), the semantic errors may stem from the fact the Eclipse/CDT project manager cannot "see" all the defined symbols, include directories, etc. that are passed to the compiler/linker options inside the makefile. In this case, your best option is to simply turn off the syntax checker as mentioned in the post below:
    e2e.ti.com/.../532289

    Another idea is to re-build the Indexer database. Something mentioned in the thread below:
    stackoverflow.com/.../eclipse-c-type-could-not-be-resolved-error-even-though-build-is-successful

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 200 points
    Dear Rafael,

    Thank you for your reply,
    Actually, I am not using makefile to build the project, I use general cross-linux project in CCS,
    Rebuilding index also doesn't really help.

    Included paths to the project can see the file i need. Project builds, however semantic error still persistent.

    Any other suggestions?

    BR,
    Ilja.