Timo Kreuzer wrote:
I am working on x64 SEH for ReactOS. The idea is to use .cfi_escape codes to mark the code positions where the try block starts / ends and of the except landing pad. The emitted .eh_frame section is parsed after linking and converted into Windows compatible unwind info / scope tables. This works quite well so far.
I always imagined that if someone wanted to do SEH, they'd actually implement it within GCC, rather than post-processing it like this. Surely you're making things too hard for yourself with these escape hacks? r~
