public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "quic_ashudas at quicinc dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/31513] New: abidiff differences due to change in compiler version
Date: Wed, 20 Mar 2024 05:57:27 +0000	[thread overview]
Message-ID: <bug-31513-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31513
           Summary: abidiff differences due to change in compiler version
           Product: libabigail
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: quic_ashudas at quicinc dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

We have created a shared library using the below source file, We are observing
abi differences as when we run abidiff on the library when compiled with
different compiler version GCC 7.5.0 and GCC 11.4.0

Ques 1: Is this behavior expected as we have not made any change in the source
files of the library the highlighted changes are in compiler source files.

Ques 2: If yes, can you share a suppression file to ignore all the changes
which  are not from the elf source file.


#include <iostream>
#include <string>
#include <vector>

namespace qiifa{

       class class1{
                public:
                        class1();
                        std::string generate_lorem_ipsum(unsigned int length);
                        int addnums(int x, int y);
                        int subnums(int x, int y);
                private:
                        std::vector<char> letters;

        };

}

Abidiff log

"Functions changes summary: 0 Removed, 1 Changed (3 filtered out), 0 Added
functions
 Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

 1 function with some indirect sub-type change:

   [C] 'method int qiifa::class1::addnums(int, int)' has some indirect sub-type
changes:
     implicit parameter 0 of type 'qiifa::class1* const' has sub-type changes:
       in unqualified underlying type 'qiifa::class1*':
         in pointed to type 'class qiifa::class1':
           type size hasn't changed
           1 data member change:
             type of 'std::vector<char, std::allocator<char> > letters'
changed:
               type size hasn't changed
               1 base class change:
                 'struct std::_Vector_base<char, std::allocator<char> >'
changed:
                   type size hasn't changed
                   1 data member change:
                     type of 'std::_Vector_base<char, std::allocator<char>
>::_Vector_impl _M_impl' changed:
                       type size hasn't changed
                       1 base class insertion:
                         struct std::_Vector_base<char, std::allocator<char>
>::_Vector_impl_data
                       3 data member deletions:
                         'std::_Vector_base<char, std::allocator<char>
>::pointer _M_start', at offset 0 (in bits)
                         'std::_Vector_base<char, std::allocator<char>
>::pointer _M_finish', at offset 64 (in bits)
                         'std::_Vector_base<char, std::allocator<char>
>::pointer _M_end_of_storage', at offset 128 (in bits)

 "

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

             reply	other threads:[~2024-03-20  5:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  5:57 quic_ashudas at quicinc dot com [this message]
2024-03-20 10:22 ` [Bug default/31513] " dodji at redhat dot com
2024-03-20 10:53 ` quic_ashudas at quicinc dot com
2024-03-20 10:54 ` quic_ashudas at quicinc dot com
2024-03-20 10:54 ` quic_ashudas at quicinc dot com
2024-03-21 10:19   ` Dodji Seketeli
2024-03-20 19:14 ` woodard at redhat dot com
2024-03-21  6:51 ` quic_ashudas at quicinc dot com
2024-03-21 10:19 ` dodji at seketeli dot org
2024-03-22  6:36 ` quic_ashudas at quicinc dot com
2024-03-22  6:36 ` quic_ashudas at quicinc dot com
2024-03-22  9:20 ` dodji at redhat dot com
2024-03-22  9:20 ` dodji at redhat dot com
2024-03-28 16:41 ` [Bug default/31513] abidiff wrongly considers data members moved to base class as harmful dodji at seketeli dot org
2024-03-29 17:40 ` dodji at seketeli dot org
2024-04-01 14:28 ` quic_ashudas at quicinc dot com
2024-04-02  9:54 ` dodji at seketeli dot org
2024-04-02 13:16 ` quic_jiafan at quicinc dot com
2024-04-03  9:58   ` Dodji Seketeli
2024-04-03  9:58 ` dodji at seketeli dot org
2024-04-03 10:22 ` quic_jiafan at quicinc dot com
2024-04-03 16:26 ` 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-31513-9487@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).