* J. W. Jagersma: > The call instruction is just a practical example. The problem I want to > address is that no exception handling information is generated at all > for asm statements. Other operations, eg. memory access, division, etc > could trap and throw an exception. The unwind tables should cover this. I think permitted uses of asm cannot do anything that would make the tables invalid, at least for DWARF unwinding information. DWARF does not need to annotate any instruction that might throw (which would be every instruction in case of asynchronous unwind tables). Thanks, Florian
