3 ms·
I call bullshit on this analysis. There's no way the code would be using integers to represent speed (they'd just be rendered as integers). >= and > are essen
by peeters 12y ago
I call bullshit on this analysis. There's no way the code would be using integers to represent speed (they'd just be rendered as integers). >= and > are essentially the same operation when comparing floating point values.
- wjy 12y agoMany processors in a modern car have no floating point capability whatsoever. Fractional numbers are represented using integers - "fixed point" representation. While it's almost certainly true that vehicle speed is calculated as a fractional value, the cruise control set speed may be an integer, as it's set in increments of 1kph (or mph, depending). There's no need to keep smaller increments. It all depends on which processor is handling the cruise control interface, and how they wrote the software. There's no way to know without more information.
- nullc 12y agoFunny. If the story was different and arguing something on the basis of floating point; I would have been posting saying that its very unlikely that the firmware was using floating point (or even running on hardware with a fast FPU).
- webXL 12y agoThe analysis doesn't claim that they're comparing integers, just the fact that it appears that you can only activate once you're very close to 31km/h or higher. It seems to contradict the manual, and therefore might be a bug or at least incomplete documentation.