Timo Kreuzer writes:
>The problem of the missing Windows x64 unwind tables is already solved!
>I generate them from DWARF2 unwind info in a postprocessing step.
Ok. The Windows unwind opcodes seemed to be much more limitted than
DWARF2's that I wouldn't have thought this approach would work.
>Th
Sorry that I only answer this late (been in the hospital for a while...)
To clear things up:
The problem of the missing Windows x64 unwind tables is already solved!
I generate them from DWARF2 unwind info in a postprocessing step.
Unwinding / stack backtraces work fine.
The problem that I have i
Kai Tietz writes:
>Hmm, yes and no. First the exception handler uses the .pdata and .xdata
>section for checking throws. But there is still the stack based exception
>mechanism as for 32-bit IIRC.
No. The mechanism is completely different. The whole point of the unwind
tables is to remove the
Hi Ross,
[EMAIL PROTECTED] wrote on 27.11.2008 23:36:22:
> Kai Tietz writes:
> >Well, you mean the SEH tables on stack.
>
> No, I mean the ABI required unwind information.
So you speak about .pdata and .xdata. Well, those aren't implemented.
First step would be to teach gas to generate those
Kai Tietz writes:
>Well, you mean the SEH tables on stack.
No, I mean the ABI required unwind information.
> Well, those aren't implemented (as they aren't for 32-bit).
64-bit SEH handling is completely different from 32-bit SEH handling.
In the 64-bit Windows ABI exceptions are handled using u
2008/11/27 Ross Ridge <[EMAIL PROTECTED]>:
> Kai Tietz writes:
>>I am very interested to learn, which parts in calling convention aren't
>>implemented for w64?
>
> Well, maybe I'm missing something but I can't any see code in GCC for
> generating prologues, epilogues and unwind tables in the format
Kai Tietz writes:
>I am very interested to learn, which parts in calling convention aren't
>implemented for w64?
Well, maybe I'm missing something but I can't any see code in GCC for
generating prologues, epilogues and unwind tables in the format required
by the Windows x64 ABI.
http://
Hi Ross,
I am very interested to learn, which parts in calling convention aren't
implemented for w64? Do you mean the SEH stack reservation? If you could
specify it more detailed, I could correct it for 4.5. I am a bit curious,
as I found that the unwind mechanism of Windows itself working quit
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 / sc
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
10 matches
Mail list logo
