public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
* [Bug default/20887] Show relative change of offset
  2016-01-01  0:00 [Bug default/20887] New: Show relative change of offset dodji at redhat dot com
@ 2016-01-01  0:00 ` dodji at redhat dot com
  2016-01-01  0:00 ` dodji at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: dodji at redhat dot com @ 2016-01-01  0:00 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=20887

dodji at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug default/20887] Show relative change of offset
  2016-01-01  0:00 [Bug default/20887] New: Show relative change of offset dodji at redhat dot com
  2016-01-01  0:00 ` [Bug default/20887] " dodji at redhat dot com
@ 2016-01-01  0:00 ` dodji at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: dodji at redhat dot com @ 2016-01-01  0:00 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=20887

dodji at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from dodji at redhat dot com ---
This feature landed in the master branch of the git repository by commit
https://sourceware.org/git/gitweb.cgi?p=libabigail.git;a=commit;h=5ed0e40bfd7ec301ec623791f940f14262f6d9ab

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug default/20887] New: Show relative change of offset
@ 2016-01-01  0:00 dodji at redhat dot com
  2016-01-01  0:00 ` [Bug default/20887] " dodji at redhat dot com
  2016-01-01  0:00 ` dodji at redhat dot com
  0 siblings, 2 replies; 3+ messages in thread
From: dodji at redhat dot com @ 2016-01-01  0:00 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=20887

            Bug ID: 20887
           Summary: Show relative change of offset
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: dodji at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

This enhancement request was filed downstream at
https://bugzilla.redhat.com/show_bug.cgi?id=1382711.  I am pasting the content
of that bug here:

It would be handy to see relative change of offset when a data member changes
its offset in a data structure. Right now we get for example this:

1 data member deletion:
  'FT_Generic FT_LibraryRec_::generic', at offset 64 (in bits) at
ftobjs.h:816:1

11 data member changes:
 'FT_Int FT_LibraryRec_::version_major' offset changed from 192 to 64 (in bits)
 'FT_Int FT_LibraryRec_::version_minor' offset changed from 224 to 96 (in bits)
 'FT_Int FT_LibraryRec_::version_patch' offset changed from 256 to 128 (in
bits)
 'FT_UInt FT_LibraryRec_::num_modules' offset changed from 288 to 160 (in bits)
 'FT_Module FT_LibraryRec_::modules[32]' offset changed from 320 to 192 (in
bits)
 'FT_ListRec FT_LibraryRec_::renderers' offset changed from 2368 to 2240 (in
bits)
 'FT_Renderer FT_LibraryRec_::cur_renderer' offset changed from 2496 to 2368
(in bits)
 'FT_Module FT_LibraryRec_::auto_hinter' offset changed from 2560 to 2432 (in
bits)
 'FT_Byte* FT_LibraryRec_::raster_pool' offset changed from 2624 to 2496 (in
bits)
 'FT_ULong FT_LibraryRec_::raster_pool_size' offset changed from 2688 to 2560
(in bits)
 'FT_DebugHook_Func FT_LibraryRec_::debug_hooks[4]' offset changed from 2752 to
2624 (in bits)


It would be great if I could see there something like this:

1 data member deletion:
  'FT_Generic FT_LibraryRec_::generic', at offset 64 (in bits) at
ftobjs.h:816:1

11 data member changes:
 'FT_Int FT_LibraryRec_::version_major' offset changed from 192 to 64 (by 128
bits)
 'FT_Int FT_LibraryRec_::version_minor' offset changed from 224 to 96 (by 128
bits)
 'FT_Int FT_LibraryRec_::version_patch' offset changed from 256 to 128 (by 128
bits)
 'FT_UInt FT_LibraryRec_::num_modules' offset changed from 288 to 160 (by 128
bits)
 'FT_Module FT_LibraryRec_::modules[32]' offset changed from 320 to 192 (by 128
bits)
 'FT_ListRec FT_LibraryRec_::renderers' offset changed from 2368 to 2240 (by
128 bits)
 'FT_Renderer FT_LibraryRec_::cur_renderer' offset changed from 2496 to 2368
(by 128 bits)
 'FT_Module FT_LibraryRec_::auto_hinter' offset changed from 2560 to 2432 (by
128 bits)
 'FT_Byte* FT_LibraryRec_::raster_pool' offset changed from 2624 to 2496 (by
128 bits)
 'FT_ULong FT_LibraryRec_::raster_pool_size' offset changed from 2688 to 2560
(by 128 bits)
 'FT_DebugHook_Func FT_LibraryRec_::debug_hooks[4]' offset changed from 2752 to
2624 (by 128 bits)


This would indicate to me that this changes are caused by the deletion of the
member "generic". But if there would be another change, I would see that in
change of the relative change more easily.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-12-02 21:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-01  0:00 [Bug default/20887] New: Show relative change of offset dodji at redhat dot com
2016-01-01  0:00 ` [Bug default/20887] " dodji at redhat dot com
2016-01-01  0:00 ` dodji at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).