Comment by dataflow

21 hours ago

How many non-8-bit-char platforms are there with char8_t support, and how many do we expect in the future?

Mostly DSPs

  • Is there a single esoteric DSP in active use that supports C++20? This is the umpteenth time I've seen DSP's brought up in casual conversations about C/C++ standards, so I did a little digging:

    Texas Instruments' compiler seems to be celebrating C++14 support: https://www.ti.com/tool/C6000-CGT

    CrossCore Embedded Studio apparently supports C++11 if you pass a switch in requesting it, though this FAQ answer suggests the underlying standard library is still C++03: https://ez.analog.com/dsp/software-and-development-tools/cce...

    Everything I've found CodeWarrior related suggests that it is C++03-only: https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/...

    Aside from that, from what I can tell, those esoteric architectures are being phased out in lieu of running DSP workloads on Cortex-M, which is just ARM.

    I'd love it if someone who was more familiar with DSP workloads would chime in, but it really does seem that trying to be the language for all possible and potential architectures might not be the right play for C++ in 202x.

    Besides, it's not like those old standards or compilers are going anywhere.

    • Cadence DSPs have C++17 compatible compiler and will be c++20 soon, new CEVA cores also (both are are clang based). TI C7x is still C++14 (C6000 is ancient core, yet still got c++14 support as you mentioned). AFIR Cadence ASIP generator will give you C++17 toolchain and c++20 is on roadmap, but not 100% sure.

      But for those devices you use limited subset of language features and you would be better of not linking c++ stdlib and even c stdlib at all (so junior developers don't have space for doing stupid things ;))

    • Green Hills Software's compiler supports more recent versions of C++ (it uses the EDG frontend) and targets some DSPs.

      Back when I worked in the embedded space, chips like ZSP were around that used 16-bit bytes. I am twenty years out of date on that space though.

      2 replies →

    • > but it really does seem that trying to be the language for all possible and potential architectures might not be the right play for C++ in 202x.

      Portability was always a selling point of C++. I'd personaly advise those who find it uncomfortable, to choose a different PL, perhaps Rust.

      2 replies →

  • Non-8-bit-char DSPs would have char8_t support? Definitely not something I expected, links would be cool.

    • Why not? except it is same as `unsigned char` and can be larger than 8 bit

      ISO/IEC 9899:2024 section 7.30

      > char8_t which is an unsigned integer type used for 8-bit characters and is the same type as unsigned char;

      1 reply →