From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 123594 invoked by alias); 7 Jun 2017 09:18:54 -0000 Mailing-List: contact libabigail-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Id: List-Subscribe: Sender: libabigail-owner@sourceware.org Received: (qmail 123522 invoked by uid 48); 7 Jun 2017 09:18:50 -0000 From: "dodji at redhat dot com" To: libabigail@sourceware.org Subject: [Bug default/21486] top-level const qualifiers on types of function parameters are not ignored Date: Sun, 01 Jan 2017 00:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed 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: dodji at redhat dot com X-Bugzilla-Status: ASSIGNED 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: Message-ID: In-Reply-To: References: 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-SW-Source: 2017-q2/txt/msg00042.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D21486 --- Comment #9 from dodji at redhat dot com --- I started to hack on this. I am categorizing changes in which top-level co= nst qualifiers of function parameter types as being harmless. As a result, tho= se changes are filtered out (by default) by libabigail. Note that users can s= till see those harmless changes by doing using the --harmless option of abidiff. Looking at the result of comparing the two attached binaries, it appears to= me that there are other things (not related to the title of this opened bug) to fix, so that abidiff concludes that the two binaries have equivalent ABIs. Ideally, I'd thus have to construct smaller test cases that expose the prob= lems separately. That way, I can use each of the small test cases as regression tests in each of the patches that resolve the problem they expose. I should thus build a version of Clang that exhibits those issues and maybe file separate bugs for the issues I am seeing. --=20 You are receiving this mail because: You are on the CC list for the bug.