This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [Patch] pe/coff x86-64: improve dump of unwind v2
- From: Tristan Gingold <gingold at adacore dot com>
- To: Corinna Vinschen <vinschen at redhat dot com>
- Cc: "binutils at sourceware dot org Development" <binutils at sourceware dot org>, Kai Tietz <ktietz at redhat dot com>
- Date: Thu, 5 Dec 2013 09:22:40 +0100
- Subject: Re: [Patch] pe/coff x86-64: improve dump of unwind v2
- Authentication-results: sourceware.org; auth=none
- References: <5FB67062-D437-4F9C-B5DF-80BEE361117B at adacore dot com> <20131204150337 dot GE8139 at calimero dot vinschen dot de>
On 04 Dec 2013, at 16:03, Corinna Vinschen <vinschen@redhat.com> wrote:
> Hi Tristan,
>
>
> thanks for following up on this with a patch. I'm just a bit confused
> about the first EPILOG info value.
For the EPILOG opcode, the 'prolog offset' byte is used differently:
> First you write:
>
> On Dec 4 15:47, Tristan Gingold wrote:
>> [...] the first EPILOG opcode contains the length of the epilogue, [...]
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
in the 'prolog offset' byte.
> Then you write:
>
>> I am not sure about the meaning of the info of the first EPILOG opcode. It looks like
>> it is set to 1 if there is an epilog at the end of the function. [...]
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(that's the info nibble).
> Which one wins?
Hopes this clarifies :-)
Tristan.