[Patch] pe/coff x86-64: improve dump of unwind v2

[Corinna Vinschen]

On Dec  5 09:22, Tristan Gingold wrote:
> 
> 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 :-)

Yes, it does.


Thank you,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20131205/6cc2dd2c/attachment.sig>