All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Diego 'Flameeyes' Pettenò"
	<flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: The strange ever-changing structure :)
Date: Mon, 12 May 2008 14:54:39 -0300	[thread overview]
Message-ID: <20080512175439.GC15306@ghostprotocols.net> (raw)
In-Reply-To: <200805121929.19084-Pa7mVGAsjv+0j3/lZWhZhlwbbkVOKVeL6HgeeWxq3HYdnm+yROfE0A@public.gmane.org>

CCing dwarves ML

Em Mon, May 12, 2008 at 07:29:17PM +0200, Diego 'Flameeyes' Pettenò escreveu:
> http://www.flameeyes.eu/tmp/dwarves-strange.tbz2
> 
> The rest of the differences are correct, I'm doing some micro-optimisation to 
> the code, but this:
> 
> ../../../src/xine-engine/alphablend.c:
>   struct header_s |  -24
>     data
>      from: uint8_t *             /*     8(0)    48(0) */
>      to:   uint8_t *             /*     8(0)    24(0) */
>  1 struct changed
> 
> 
> I always find in my codiff outputs...

Using readelf we can see that we have two header_s definitions:

One that is local to the blend_yuy2_grow_extra_data function and has 32
bytes:

 <2><5d2b2>: Abbrev Number: 19 (DW_TAG_structure_type)
    <5d2b3>   DW_AT_name        : (indirect string, offset: 0x79c6): header_s   
    <5d2b7>   DW_AT_byte_size   : 32    
    <5d2b8>   DW_AT_decl_file   : 1     
    <5d2b9>   DW_AT_decl_line   : 1549  
    <5d2bb>   DW_AT_sibling     : <0x5d2ec>

And another, that is local to the blend_yuv_grow_extra_data function and
that has 56 bytes.

 <2><5d401>: Abbrev Number: 19 (DW_TAG_structure_type)
    <5d402>   DW_AT_name        : (indirect string, offset: 0x79c6): header_s   
    <5d406>   DW_AT_byte_size   : 56    
    <5d407>   DW_AT_decl_file   : 1     
    <5d408>   DW_AT_decl_line   : 1107  
    <5d40a>   DW_AT_sibling     : <0x5d43b> 

I'm now thinking on how to properly support this... I think that the
data structures in libdwarves are in the right shape, i.e. these structs
already are in separate namespaces, I'll check now how pahole/codiff are
handling this.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2008-05-12 17:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200805121929.19084-Pa7mVGAsjv+0j3/lZWhZhlwbbkVOKVeL6HgeeWxq3HYdnm+yROfE0A@public.gmane.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080512175439.GC15306@ghostprotocols.net \
    --to=acme-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.