Re: ABI Compliance Checker GSoC Project

Hello Hackers,
I have been working on this project with David since last month.
I've written some blogs about the progress, the most recent one is here [1]
Here's the draft pull request for anyone interested in reviewing the code: [2]

On Wed, 9 Jul 2025 at 17:57, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> Were you able to make any progress on this?
For now, my goal was to make it work without handling false positives.
I plan to address those later, but I want to understand them now so I
can move faster when the time comes.

On Wed, 9 Jul 2025 at 21:03, Andres Freund <andres(at)anarazel(dot)de> wrote:
> This is beneficial for extensions because on ELF platforms, all exported
> platforms in shared libraries can be intercepted by the main executable,
> requiring all function calls between exported functions within an extension to
> go through the GOT, slowing things down noticeably.
>
>
> > Anyway, it doesn't look to me like adding -fvisibility=hidden to CFLAGS is a
> > viable solution, though maybe it is possible to get the build to play nice.
>
> It'd be nice if we could get there, but it'd require annotating *all*
> intentionally exported functions in the backend with PGDLLIMPORT (rather than
> just doing that for variables). Then we could make some symbols
> *intentionally* not exported, which can improve the code generation (allowing
> more compiler and linker optimizations).
Thanks for the explanation, Andres!
Had the same questions as David asked.

Regards,
Mankirat

[1] - https://blog.mankiratsingh.com/posts/worklog-3to11-abi-complicance-reporting/
[2] - https://github.com/PGBuildFarm/client-code/pull/38