3 ms·
Testing on a desktop machine with many cores is not a good simulation of that environment. You run your tests on your local machine as much as possible. Then
by bluGill 2y ago
Testing on a desktop machine with many cores is not a good simulation of that environment. You run your tests on your local machine as much as possible. Then you run on the real production hardware enough tests to be confident.
I don't work automotive, but my application is very similar - an embedded display running ARM CPUs. I do a lot of testing on x86-64 and only rarely encounter portability issues. When I do discover such things they have always been things that I need real hardware to debug on not something an ARM desktop would help with.
- cbsmith 2y agoI'm guessing then you've never had to deal with optimizer bugs.
- bluGill 2y agoI have they are rare though. once ever 10 years for a good sized project seems right. Where they habpen I wouldn't expect anything other than the exact hardware to reproduce them so I'm still not wanting a workstation live the target.
- cbsmith 2y agoI've run into tons of optimizer bugs. While it's possible they would require the exact hardware to reproduce them, that has never been the case. Generally you just need something to run the actual output of the optimizer. You can even reproduce the bugs in emulators, it just takes way longer. Most optimizer bugs are about the optimizer making assumptions about properties of the source code, not assumptions about properties of the hardware. Certainly it can go both ways, but of course you want to test the actual output of the optimizer. Doing otherwise is not at all what I'd call standard practice.