Re: Autodetection of packages that need visibility annotations

2018-05-16 Thread Yuri Gribov
On Wed, May 16, 2018 at 2:32 AM, Paul Wise wrote: > The 'adequate' tool does some of that: > > missing-symbol-version-information > symbol-size-mismatch > undefined-symbol > > https://packages.debian.org/unstable/adequate Thanks, that's a nice one (what a relief to read Perl rather than Python).

Re: Autodetection of packages that need visibility annotations

2018-05-15 Thread Yuri Gribov
On Tue, May 15, 2018 at 10:56 AM, Simon McVittie wrote: > On Tue, 15 May 2018 at 10:44:27 +0100, Yuri Gribov wrote: >> On Tue, May 15, 2018 at 9:22 AM, Andrey Rahmatullin wrote: >> > There is an interesting question about this: technically speaking, >> > removing

Re: Autodetection of packages that need visibility annotations

2018-05-15 Thread Yuri Gribov
On Tue, May 15, 2018 at 9:22 AM, Andrey Rahmatullin wrote: > There is an interesting question about this: technically speaking, > removing exported symbols requires a soname bump. But one can say that > those symbols were never public and so they are not a part of ABI. > Fixing this upstream and b

Re: Autodetection of packages that need visibility annotations

2018-05-15 Thread Yuri Gribov
On Tue, May 15, 2018 at 7:28 AM, Paul Wise wrote: > In case you would like to get this (or your other QA tools) into > Debian, I would be happy to sponsor you. Thanks Paul, that's very inspiring! I would be glad to work on integration to Debian if community decides that tool(s) are useful. -Y

Autodetection of packages that need visibility annotations

2018-05-14 Thread Yuri Gribov
Hi all, Linux shared libraries by default allow for runtime interposition of symbols. This comes in handy for customization of malloc but might also have undesired consequences. Firstly, it badly affects performance of generated code as 1) compiler is not allowed to optimize (inline/clone/split) f