Gregory M. Turner wrote:
On Wednesday 14 May 2003 11:08 pm, Alexandre Julliard wrote:
(I don't want to discourage you, but I think you will eventually come to realize that the only way to make this work right is to do it in the compiler)
Don't worry, we are in agreement on this. I have spent a fair amount of time trying to decide whether this problem is fixable without such a measure, and I suspect the answer is no, or, at least, not without doing an inordinate amount of work and writing lots of asm.
[snip]
When/if gcc does it, great, we just use the implementation of __TRY in terms of __try, we don't have to change a thing. If, for example, after some research, the -fasync-unwind-tables thing pans out, that's fine too; we can add that in, but not all platforms support this, even for gcc, so we still need a pure-C portable alternative to be supported by wine to some reasonable extent.
Has anyone investigated what work needs to be done for gcc to support these kinds of try/except things?