@SwiftOnSecurity I can't give away details, but in discussions with one of the large European auto manufacturers about their technology, they mentioned that their current cars have over 50 unique ARM processors of various specs and capabilities in them, and that number was expected to exceed 100 shortly. (This was pre pandemic chip shortage.)
Your car isn't a CPU. It's a distributed compute cluster.
@philip @SwiftOnSecurity I guess it depends on what you consider "necessary". What's the core functionality? What's the market differentiator? What are the alternatives that wouldn't increase the cost of the vehicle itself, or its R&D significantly?
There are well-established benefits to be had re-using exiting tooling at manufacturing scale.
@carmencr @philip @SwiftOnSecurity Given the way car manufacturers write code, there’s a lot to be said for chopping it up into small pieces on separate CPUs, if only to force them not to use 10,000 global variables.
https://www.embedded.com/why-every-embedded-software-developer-should-care-about-the-toyota-verdict/
@carmencr @SwiftOnSecurity ...and a cluster that talks with horribly outdated and basically unfixable protocols by BOSCH, to boot.
(IIRC the way those famous exploits that could make Fiat-Chrysler cars break suddenly through a hacked infotainment were rather simple floods of malicious packets)
I was pretty sure that I had read that some high-end cars were already over 100 processors. There's a big push in this space to try to consolidate some of the workloads, including by containerizing as much as they can and running it on one bigger, multicore system. Fascinating.