public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19173] Abidiff doesn't detect symbol size change in library.
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <bug-19173-9487-O41KgkfCbI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19173-9487@http.sourceware.org/bugzilla/>

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

--- Comment #15 from dodji at redhat dot com ---
(In reply to Jakub Jelinek from comment #4)
> Bet that is because abidiff looks at the debug info, which in this case
> doesn't reflect the bogus size change either.  In GCC, the size of the
> symbol is never changed, because it is an ABI change, we just insert padding
> after the symbol.

I gave this some more thoughts.

For a function, the size of the underlying symbol is the size taken by the
function in the .text segment.

So a change of that size does not indicate an ABI change.

For a global variable, however, I think it's different.  In that case, the size
of the symbol is the size of the storage occupied by the variable.  In theory
that size should match the size of the type of that variable.  And a change in
that size is an ABI change.

So I think we should detect symbol size changes for variables, only.

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

  parent reply	other threads:[~2015-11-06 14:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 [Bug default/19173] New: " m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` [Bug default/19173] " jakub at redhat dot com
2015-01-01  0:00 ` mjw at redhat dot com
2015-01-01  0:00 ` dodji at redhat dot com
2015-01-01  0:00 ` y.gribov at samsung dot com
2015-01-01  0:00 ` dodji at redhat dot com [this message]
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` dodji at redhat dot com
2015-01-01  0:00 ` y.gribov at samsung dot com
2015-01-01  0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` jakub at redhat dot com
2015-01-01  0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` y.gribov at samsung dot com
2015-01-01  0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01  0:00 ` dodji at seketeli dot 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=bug-19173-9487-O41KgkfCbI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@sourceware.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 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).