• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 170 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.

TMS570LC4357: C++ compiler errors

Ali Ghadyali
Prodigy 40 points
Part Number: TMS570LC4357


I have a project which compiles fine when using C99. I want to build using C++. The project compiles fine, so I do not use CPP STL libraries. Custom classes without using any STL or std CPP libraries compile. Ok!

List of Errors 

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\yvals.h", line 395: remark #195-D:
zero used for undefined preprocessing identifier "__STDC_VERSION__"
#if 199901L <= __STDC_VERSION__
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\cstdio", line 18: remark #195-D:
zero used for undefined preprocessing identifier "_HAS_DINKUM_CLIB"
#if defined(__TI_COMPILER_VERSION__) && !_HAS_DINKUM_CLIB
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\new", line 105: remark #885-D:
support for placement delete is disabled
void operator delete(void *, const _STD nothrow_t&)
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\new", line 108: remark #885-D:
support for placement delete is disabled
void operator delete[](void *, const _STD nothrow_t&)
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\new", line 111: remark #885-D:
support for placement delete is disabled
void operator delete(void *, void *) _THROW0();
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\new", line 114: remark #885-D:
support for placement delete is disabled
void operator delete[](void *, void *) _THROW0();
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 8: remark #195-D:
zero used for undefined preprocessing identifier
"_HAS_ITERATOR_DEBUGGING"
#if _HAS_ITERATOR_DEBUGGING
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 633: remark #195-D:
zero used for undefined preprocessing identifier
"_HAS_ITERATOR_DEBUGGING"
#if _HAS_ITERATOR_DEBUGGING
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 780: remark #195-D:
zero used for undefined preprocessing identifier
"_HAS_ITERATOR_DEBUGGING"
#if _HAS_ITERATOR_DEBUGGING
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 794: remark #195-D:
zero used for undefined preprocessing identifier
"_HAS_ITERATOR_DEBUGGING"
#if _HAS_ITERATOR_DEBUGGING
^

"C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 862: remark #195-D:
zero used for undefined preprocessing identifier
"_HAS_ITERATOR_DEBUGGING"
#if _HAS_ITERATOR_DEBUGGING
^

INTERNAL ERROR: C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\armacpia.exe experienced a segmentation fault
while processing function operator- file C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility line 1026

  • 0
    TI__Guru**** 251290 points

    It is a known problem that the C++ header files do not build clean with --issue_remarks.  Unfortunately, this issue is not fixed.  As a workaround, do not build with --issue_remarks.  I think that will fix ...

    Ali Ghadyali said:
    INTERNAL ERROR: C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\armacpia.exe experienced a segmentation fault
    while processing function operator- file C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility line 1026

    If it doesn't, then I need a test case which allows me to reproduce the problem.  For the source file being compiled when this occurs, please follow the directions in the article How to Submit a Compiler Test Case.

    I notice you use ARM compiler version 5.1.6.  This compiler is about 8 years old.  If it is practical, upgrade to a more recent version.  At this time, the most recent version is 20.2.6.LTS.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 40 points

    Hi George,

    Thanks for the reply. I had to remove  --check_misra=none for the program to compile. I see a lot of remarks in the output file now. 

    "C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\yvals.h", line 395: remark #195-D: zero used for undefined preprocessing identifier "__STDC_VERSION__"
    "C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\cstdio", line 18: remark #195-D: zero used for undefined preprocessing identifier "_HAS_DINKUM_CLIB"
    "C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\new", line 105: remark #885-D: support for placement delete is disabled

    "C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 862: remark #195-D: zero used for undefined preprocessing identifier "_HAS_ITERATOR_DEBUGGING"
    "C:\TI\ccs1110\ccs\tools\compiler\arm_5.1.6\bin\..\include\xutility", line 1241: remark #195-D: zero used for undefined preprocessing identifier "_IS_EMBEDDED"

    Do I just define these in the makefile?

    Ali

  • +1 in reply to Ali Ghadyali
    TI__Guru**** 251290 points
    Ali Ghadyali said:
    Do I just define these in the makefile?

    No.  Do not use the compiler option --issue_remarks.

    Thanks and regards,

    -George