5 ms·
Easy, go hunting their manuals for the compilers that aren't yet another clang fork, still a few around between TI, Microchip and co on embedded. In general, n
by pjmlp 1y ago
Easy, go hunting their manuals for the compilers that aren't yet another clang fork, still a few around between TI, Microchip and co on embedded.
In general, not for Qt deployment scenarios, also take into consideration the surviving big iron UNIX, mainframes and micros still in business, again the compilers that are yet not clang forks.
The table is a non exaustive overview, however it also paints the picture that for those that care about real portable code, regular visits to the table are required before considering adopting any specific new feature, or the need to enforce style guides like "we use C++20, but feature X, Y, Z are forbidden due to lack of portablity".
- detaro 1y agoBut Qt doesn't care for microcontrollers, nor mainframes. The most exotic target they have is QNX, but "Qt needs C++XX" seems to be a pretty good motivator for QNX to update their compilers, which are gcc-based after all.
- pjmlp 1y agoThey care about all of these, https://doc.qt.io/qt-6/supported-platforms.html https://doc.qt.io/qt-6/supported-platforms.html I do see exotic stuff like INTEGRITY as well, still the point stands all those platforms listed on the page have to support C++26 in the Compiler column as the reference compiler.