lkml.org 
[lkml]   [2023]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v2 0/2] Validating UAPI backwards compatibility
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.
--
Thanks,
~Nick Desaulniers

\
 
 \ /
  Last update: 2023-03-27 00:40    [W:0.145 / U:0.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site