From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9B4E63857C59; Thu, 29 Oct 2020 10:08:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9B4E63857C59 From: "gprocida+abigail at google dot com" To: libabigail@sourceware.org Subject: [Bug default/26807] New: Issues with enum-underlying types Date: Thu, 29 Oct 2020 10:08:11 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gprocida+abigail at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: libabigail@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Mailing list of the Libabigail project List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2020 10:08:11 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26807 Bug ID: 26807 Summary: Issues with enum-underlying types Product: libabigail Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: default Assignee: dodji at redhat dot com Reporter: gprocida+abigail at google dot com CC: libabigail at sourceware dot org Target Milestone: --- Hi. I've posted an RFC patch which illustrates a few issues with libabigail's treatment of enum-underlying types. https://sourceware.org/pipermail/libabigail/2020q4/002788.html Repeating them here: - signedness and changes thereof (as seen in DWARF) are not modelled - size and alignment changes are reported twice - size changes are not considered ABI incompatibilities - *all* enum-underlying types are currently considered anonymous and have the same name, even when they differ in size, alignment or signedness=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 The last item is closely related to the others but is troublesome in a different way. It can cause non-deterministic ordering of such types in XML output (in the presence of concurrent heap-allocation by other threads). In particular, it causes test flakiness. I've not attempted to find a way that signedness changes can cause API surprises. However, there are mentions of undefined behaviour that may occur when casting in https://en.cppreference.com/w/cpp/language/enum. --=20 You are receiving this mail because: You are on the CC list for the bug.=