How are exceptions actually implemented in assembly?

[Aahz Maruch]

In article <B875F6C2.36FB%jonathan at onegoodidea.com>,
Jonathan Hogg  <jonathan at onegoodidea.com> wrote:
>On 23/1/2002 22:06, in article a2nc5d$75a$1 at panix2.panix.com, "Aahz Maruch"
><aahz at panix.com> wrote:
>> In article <mailman.1011809616.25217.python-list at python.org>,
>> hungjunglu <hungjunglu at yahoo.com> wrote:
>>> 
>>> [...] Python exception
>>> handling is at much higher level, and it charges this cost at that
>>> level. Not too bad, in a sense, since the underlying C code does not
>>> necessarily have to propagate the exception handling all the way down
>>> to assembly. But, it also means that at Python level, exception is
>>> built into everywhere. That's OK, I guess... compared to other things
>>> (e.g: variable name look up), exception handling is probably pretty
>>> cheap in resources/performance.
>> 
>> Note carefully that the cost comes almost entirely during the handling
>> of exceptions, not in setting up exception blocks.  So if as a
>> percentage of instructions executing exceptions are rare, it's a very
>> small penalty.
>
>On the contrary, I think the original explanation is most accurate. The cost
>of exception handling in Python is pretty much O(n) in the number of Python
>"instructions" executed in total.
>
>At each point that a C call returns in the interpreter (or extension
>modules), the return pointer is checked to see if it is NULL (indicating an
>exception) and appropriate error handling is invoked if it is - usually just
>returning from the current function with NULL, i.e., unwinding the stack.
>
>Thus a constant is added to the cost of every Python instruction. This
>constant is small (the cost of a register-equal-to-zero and a
>not-taken-conditional-branch) but still there.
>
>Thus, Python exception handling is indeed "built into everywhere". You pay a
>penalty for Python having exceptions rather than a penalty for choosing to
>use them.
>
>[And yes, in comparison to all the other overhead of a dynamic interpreted
>language it is very cheap.]

While your point makes sense, I got the impression that the discussion
was in the context of whether to choose to use exceptions as part of
one's Python program.  From that standpoint, my comment is more
accurate.  If the context is language design in general, your analysis is
more accurate.
-- 
                      --- Aahz  <*>  (Copyright 2002 by aahz at pobox.com)

Hugs and backrubs -- I break Rule 6                 http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista   

"I support family values -- Addams family values" --www.nancybuttons.com