• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 888 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.

STL numeric_limits is_signed do not work

Thomas S
Intellectual 600 points

Other Parts Discussed in Thread: OMAPL138

I tested the following STL instructions on an ARM (TMS470: OMAPL138)

bool sig1=std::numeric_limits<unsigned char>::is_signed;
bool sig2=std::numeric_limits<char>::is_signed;

Unfortunately both return false.

Is this a known issue? Is there a solution?

  • 0
    Intellectual 600 points

    I found out there seems to be a difference between "signed char" and "char".

    bool sig1=std::numeric_limits<unsigned char>::is_signed;
    bool sig2=std::numeric_limits<signed char>::is_signed;

    sig1 returns false.
    sig2 returns true.

    I always thought char is signed by default?

  • 0 in reply to Thomas S
    TI__Guru* 84285 points

    It is implementation-defined whether "plain" char is signed or unsigned.

    For ARM, it defaults to unsigned.  You can change this behavior with the option --plain_char=signed, but this will create object files that are not compatible with unsigned plain char.  You should probably stick to the default.