public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28319] New: abidw - regression in treatment of anonymous enums in structs
Date: Wed, 08 Sep 2021 14:28:08 +0000	[thread overview]
Message-ID: <bug-28319-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28319
           Summary: abidw - regression in treatment of anonymous enums in
                    structs
           Product: libabigail
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: gprocida at google dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

This has been seem with kernels like:

https://ci.android.com/builds/submitted/7705975/kernel_abi_aarch64/latest/vmlinux

Current master conflates the anonymous enums in struct net_device and struct
drm_buf.

Comparing old (a test case, so perhaps fairly old) XML and newly-generated XML
gives diffs like:

[...]
                                      in pointed to type 'struct drm_buf' at
drm_legacy.h:50:1:
                                        type size hasn't changed
                                        1 data member changes (2 filtered):
                                          type of '__anonymous_enum__ list'
changed:
                                            type size hasn't changed
                                            6 enumerator deletions:
                                             
'__anonymous_enum__::DRM_LIST_NONE' value '0'
                                             
'__anonymous_enum__::DRM_LIST_FREE' value '1'
                                             
'__anonymous_enum__::DRM_LIST_WAIT' value '2'
                                             
'__anonymous_enum__::DRM_LIST_PEND' value '3'
                                             
'__anonymous_enum__::DRM_LIST_PRIO' value '4'
                                             
'__anonymous_enum__::DRM_LIST_RECLAIM' value '5'
                                            6 enumerator insertions:
                                             
'__anonymous_enum__1::NETREG_UNINITIALIZED' value '0'
                                             
'__anonymous_enum__1::NETREG_REGISTERED' value '1'
                                             
'__anonymous_enum__1::NETREG_UNREGISTERING' value '2'
                                             
'__anonymous_enum__1::NETREG_UNREGISTERED' value '3'
                                             
'__anonymous_enum__1::NETREG_RELEASED' value '4'
                                             
'__anonymous_enum__1::NETREG_DUMMY' value '5'

[...]

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

             reply	other threads:[~2021-09-08 14:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 14:28 gprocida at google dot com [this message]
2021-09-08 14:45 ` [Bug default/28319] " gprocida at google dot com
2021-09-08 15:23 ` dodji at redhat dot com
2021-09-08 16:00 ` woodard at redhat dot com
2021-09-21 15:27 ` dodji at redhat dot com
2021-10-08 10:53 ` gprocida at google dot com
2022-01-11 11:30 ` gprocida at google dot com
2022-01-11 12:36 ` gprocida at google dot com
2022-01-11 17:01 ` dodji at redhat dot com
2022-01-11 18:16 ` gprocida at google dot com
2022-01-12 11:25 ` gprocida at google dot com
2022-01-12 11:59 ` gprocida at google dot com
2022-01-13 11:01 ` gprocida at google dot com
2022-01-13 13:35 ` dodji at redhat dot com
2022-01-13 14:26 ` gprocida at google dot com
2022-01-14 12:38 ` dodji at redhat dot com
2022-01-24 17:06 ` gprocida at google dot com
2022-03-01 11:22   ` Dodji Seketeli
2022-03-01 11:22 ` dodji at seketeli dot org
2022-03-01 14:56 ` gprocida at google dot com
2022-03-01 14:59 ` gprocida at google dot com

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-28319-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).