public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: John Moon <quic_johmoo@quicinc.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-arm-msm@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Bjorn Andersson <andersson@kernel.org>,
	Todd Kjos <tkjos@google.com>,
	Matthias Maennich <maennich@google.com>,
	Giuliano Procida <gprocida@google.com>, <kernel-team@android.com>,
	<libabigail@sourceware.org>, Jordan Crouse <jorcrous@amazon.com>,
	Trilok Soni <quic_tsoni@quicinc.com>,
	"Satya Durga Srinivasu Prabhala" <quic_satyap@quicinc.com>,
	Elliot Berman <quic_eberman@quicinc.com>
Subject: Re: [PATCH v2 0/2] Validating UAPI backwards compatibility
Date: Wed, 1 Mar 2023 11:24:15 -0800	[thread overview]
Message-ID: <0c92e7b8-e415-8ad5-14e7-d94f18c3fa25@quicinc.com> (raw)
In-Reply-To: <41d287fa-3a0a-cac6-4595-ad47ef873d79@quicinc.com>

On 3/1/2023 10:03 AM, John Moon wrote:
> On 3/1/2023 9:50 AM, Nick Desaulniers wrote:
>> On Tue, Feb 28, 2023 at 11:54 PM John Moon <quic_johmoo@quicinc.com> 
>> wrote:
>>>
>>> Currently, the script works with gcc. It generates output like this when
>>> a backwards-incompatible change is made to a UAPI header:
>>>
>>>   !!! ABI differences detected in include/uapi/linux/acct.h (compared to
>>>   file at HEAD^1) !!!
>>>
>>>       [C] 'struct acct' changed:
>>>         type size changed from 512 to 544 (in bits)
>>>         1 data member insertion:
>>>           '__u32 new_val', at offset 512 (in bits) at acct.h:71:1
>>>
>>>   0/1 UAPI header file changes are backwards compatible
>>>   UAPI header ABI check failed
>>>
>>> However, we have not had success with clang. It seems clang is more
>>> aggressive in optimizing dead code away (no matter which options we
>>> pass). Therefore, no ABI differences are found.
>>
>> Hi John,
>> Do you have the list of bugs you've filed upstream against clang wrt.
>> information missing when using `-fno-eliminate-unused-debug-types`?
>>
>> https://github.com/llvm/llvm-project/issues is the issue tracker.
>>
>> Seeing a strong participant in both the Android and LLVM ecosystems
>> supply scripts that lack clang support...raises eyebrows.
> 
> We have not filed a bug with upstream clang since we're not sure it's 
> *not* and issue on our end. Giuliano Procida (CC'd) has tested the 
> script with clang 13 and 14 and GCC 10, 11 and 12 and got the expected 
> diff. If it's convenient for anyone testing this script to give it a 
> whirl with clang and report back, it could help us determine if there's 
> a real issue with clang support. :)

With some additional internal testing, we've found that clang does not 
work with this script on Ubuntu 18.04, but does work on Ubuntu 20.04. 
This is controlling for the clang version and different installation 
sources. The same clang-15 binary run on an 18.04 host fails while 
working on 20.04.

We'll investigate some more internally and potentially file a bug with 
upstream clang.

  reply	other threads:[~2023-03-01 19:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  7:54 John Moon
2023-03-01  7:54 ` [PATCH v2 1/2] check-uapi: Introduce check-uapi.sh John Moon
2023-03-03 21:09   ` Dodji Seketeli
2023-03-05  4:22   ` Masahiro Yamada
2023-03-05 17:08     ` John Moon
2023-03-01  7:54 ` [PATCH v2 2/2] docs: dev-tools: Add UAPI checker documentation John Moon
2023-03-05  6:20   ` Masahiro Yamada
2023-03-06 16:56     ` John Moon
2023-03-01 17:50 ` [PATCH v2 0/2] Validating UAPI backwards compatibility Nick Desaulniers
2023-03-01 18:03   ` John Moon
2023-03-01 19:24     ` John Moon [this message]
2023-03-01 22:33       ` John Moon
2023-03-01 23:33         ` Nick Desaulniers
2023-03-01 23:35           ` Trilok Soni
2023-03-01 23:52         ` Mark Wielaard
2023-03-01 23:59           ` John Moon
2023-03-10  8:09 ` Christoph Hellwig
2023-03-10 18:20   ` Trilok Soni
2023-03-20  6:26     ` Christoph Hellwig

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=0c92e7b8-e415-8ad5-14e7-d94f18c3fa25@quicinc.com \
    --to=quic_johmoo@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gprocida@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jorcrous@amazon.com \
    --cc=kernel-team@android.com \
    --cc=libabigail@sourceware.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maennich@google.com \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=quic_eberman@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --cc=rdunlap@infradead.org \
    --cc=tkjos@google.com \
    /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).