3 ms·
Part of the issue is that the interrupt number, 5, is hard-wired. So there really was no need to keep it alive.
by stassats 11y ago
Part of the issue is that the interrupt number, 5, is hard-wired. So there really was no need to keep it alive.
- userbinator 11y agoDivide-by-zero has always been interrupt 0, and the page fault is at #14, and that hasn't been problematic... BOUND does raise an exception if it fails but I think that's a good thing - if code is doing array bounds-checking, OOB accesses are very likely to be a bug (and possible security vulnerability) so aborting execution by default is the right thing to do.