What exactly happens when a DivisionByZero exception is thrown?










0















What up my fellows? Hope you guys are great! All right, today I’ve got something stuck in my head: What happens when a DivisionByZero exception is thrown? I mean, what is going on internally?
If you have already studied computer architecture, you know that divisions are a sequence of subtractions made by the Logic and Arithmetic Unity. For example, eight divided by four is simply four subtracted from eight twice. We subtract until we can’t subtract anymore.
So, when we want to divide, for example, 8 by 0, we want to subtract zero from eight zero times. So, I would like to know what exactly happens when our CPU has to face this, does it simply stop and the execution is aborted?










share|improve this question

















  • 4





    First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

    – Peter Cordes
    Nov 14 '18 at 3:37
















0















What up my fellows? Hope you guys are great! All right, today I’ve got something stuck in my head: What happens when a DivisionByZero exception is thrown? I mean, what is going on internally?
If you have already studied computer architecture, you know that divisions are a sequence of subtractions made by the Logic and Arithmetic Unity. For example, eight divided by four is simply four subtracted from eight twice. We subtract until we can’t subtract anymore.
So, when we want to divide, for example, 8 by 0, we want to subtract zero from eight zero times. So, I would like to know what exactly happens when our CPU has to face this, does it simply stop and the execution is aborted?










share|improve this question

















  • 4





    First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

    – Peter Cordes
    Nov 14 '18 at 3:37














0












0








0








What up my fellows? Hope you guys are great! All right, today I’ve got something stuck in my head: What happens when a DivisionByZero exception is thrown? I mean, what is going on internally?
If you have already studied computer architecture, you know that divisions are a sequence of subtractions made by the Logic and Arithmetic Unity. For example, eight divided by four is simply four subtracted from eight twice. We subtract until we can’t subtract anymore.
So, when we want to divide, for example, 8 by 0, we want to subtract zero from eight zero times. So, I would like to know what exactly happens when our CPU has to face this, does it simply stop and the execution is aborted?










share|improve this question














What up my fellows? Hope you guys are great! All right, today I’ve got something stuck in my head: What happens when a DivisionByZero exception is thrown? I mean, what is going on internally?
If you have already studied computer architecture, you know that divisions are a sequence of subtractions made by the Logic and Arithmetic Unity. For example, eight divided by four is simply four subtracted from eight twice. We subtract until we can’t subtract anymore.
So, when we want to divide, for example, 8 by 0, we want to subtract zero from eight zero times. So, I would like to know what exactly happens when our CPU has to face this, does it simply stop and the execution is aborted?







exception logic cpu-architecture divide-by-zero






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 14 '18 at 1:36









Luiz Augusto VenturaLuiz Augusto Ventura

11




11







  • 4





    First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

    – Peter Cordes
    Nov 14 '18 at 3:37













  • 4





    First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

    – Peter Cordes
    Nov 14 '18 at 3:37








4




4





First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

– Peter Cordes
Nov 14 '18 at 3:37






First of all, real ALUs don't implement division by repeated subtraction, they use much more efficient algorithms. They'd normally just check the divisor for zero in parallel with starting up the process of whatever they actually do, and raise an exception if there's a problem. What CPU architecture are you asking about? On x86, #DE (divide exception) has its own entry in the interrupt descriptor table (IDT) and works like other exceptions (page fault, general protection fault, invalid instruction, etc). wiki.osdev.org/Exceptions

– Peter Cordes
Nov 14 '18 at 3:37













0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291947%2fwhat-exactly-happens-when-a-divisionbyzero-exception-is-thrown%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291947%2fwhat-exactly-happens-when-a-divisionbyzero-exception-is-thrown%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

Syphilis

Darth Vader #20