Reminds me of Greenhills' embedded C/C++ toolchain.
I've only ever had to use it at two places. We'd find compiler bugs and report them for which we were barely even given an acknowledgement after they'd finally agreed that it wasn't that we were 'using the programming language wrong'. If we needed to have them fixed in a timely manner, we were required to pay gouging amounts for a patch.
Greenhills gets used a lot for safety critical because they claim certification to various standards but you have to pay them again to get proof of that.
I've pointed out to management that as gcc is so widely used and open source that is easy to use those facts and a good test suite (which you need anyway regardless of toolchain) to demonstrate its fitness for SC software to the satisfaction of almost all regulatory standards. Even when I show them that I've been able to do that for other clients they still insist on using Greenhills while simultaneously complaining about the engineering budget.