Re:A Guide to Undefined Behavior in C and C++
by tempest_ on Thursday August 17, 2023 @07:01PM
(#37169397)
Are they actually bespoke compilers, or just some decade old fork of gcc that works for that chipset and is never updated again?
( I am not being facetious )
Re:A Guide to Undefined Behavior in C and C++
by sigsev_251 on Friday August 18, 2023 @03:02AM
(#37172212)
From my experience, while many MCUs have settled for the big compilers (GCC and Clang), DSPs and some FPGAs (not Intel and Xilinx, those have lately settled for Clang and a combination of Clang and GCC respectively) use some pretty bespoke compilers (just running ./<compiler> --version is enough to verify this, if the compiler even offers that option). That's not necessarily bad, since many of them offer some really useful features, but error messages can be really cryptic in some cases. Also some industries require use of verified compilers, like CompCert[1], and in such cases GCC and Clang just don't cut it.
Re:A Guide to Undefined Behavior in C and C++
by marcosdumay on Thursday August 17, 2023 @07:06PM
(#37169457)
Well, nowadays you are supposed to port a backend, and not write an entire compiler.
Someone at a chip manufacturer writing something for a brand new chipset, for example. It takes a long time to get stuff shoved into GCC. It's only in recent history has life settled on one or two "big" compilers. There are still plenty of other places where you will find bespoke compilers. Perhaps not commonly, but they do exist (especially in embedded).