• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 603 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VL-Q1: C7X DSP : got an error using the stream engine under the condition of vectypes=off

Mengqi LU
Prodigy 30 points
Part Number: TDA4VL-Q1
Other Parts Discussed in Thread: TDA4VL

Hi , TI experts,

       On the C7X of TDA4VL, due to code legacy issues, we had to close the vector data type and use the vector data type with double underscores.

When using the stream engine, we encountered the following problems：

identifier "__se_ac___short32" is undefined when using __SE0ADV

 

        __SE_TEMPLATE_v1 se_params = __gen_SE_TEMPLATE_v1();
        __SE0_OPEN((void*)inArray, se_params);
        
        __short32 vOut = (__short32)(0);   //Compile OK
        __short32 vIn  = __SE0ADV(__short32);// <--- identifier "__se_ac___short32" is undefined

  • 0
    Prodigy 30 points

    hi ，Add some information here, the CGT version we use is ti-cgt-c7000_3.0.0.STS_linux

  • 0 in reply to Mengqi LU
    TI__Guru**** 249860 points

    Thank you for informing us of this issue.  I can reproduce the same behavior.  I filed the entry EXT_EP-11156 to have it investigated.  You are welcome to follow it with that link.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 30 points

    Hi George,

    I can't track the latest status of this issue, it still shows processing

    If this problem is fixed, will it be updated in the latest SDK version or will provide a hot patch corresponding to the current SDK ...

  • 0 in reply to Mengqi LU
    TI__Guru**** 249860 points

    The problem is more general than the case you have found.  Unless specific type names are used, the macros __SE0ADV, __SE1ADV, __SE0, and __SE1 do not work.  The type name __short32 is but one example of the problem.  Type names that are const qualified, or created with typedefs, also do not work.  There is a plan to address this broader issue.  It requires changes to the compiler, and the implementation of those macros.  At this point, there is no schedule for implementation.  Once it is implemented, no changes will be required in the SDK, beyond the usual testing with a new compiler.

    Thanks and regards,

    -George