Hi,
On 2023-10-18 21:29:37 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > It turns out that updating the in-tree typedefs.list would be very noisy. On
> > my local linux system I get
> > 1 file changed, 422 insertions(+), 1 deletion(-)
> > On a mac mini I get
> > 1 file changed, 351 insertions(+), 1 deletion(-)
>
> That seems like it needs a considerably closer look. What exactly
> is getting added/deleted?
Types from bison, openssl, libxml, libxslt, icu and libc, at least. If I
enable LLVM, there are even more.
(I think I figured out what's happening further down)
> > We could possibly address that by updating the in-tree typedefs.list a bit
> > more aggressively. Sure looks like the source systems are on the older side.
>
> Really? Per [1] we've currently got contributions from calliphoridae
> which is Debian sid, crake which is Fedora 38, indri/sifaka which are
> macOS Sonoma. Were you really expecting something newer, and if so what?
It's quite odd, I see plenty more types than those. I can't really explain why
they're not being picked up on those animals.
E.g. for me bison generated files contain typedefs like
typedef int_least8_t yytype_int8;
typedef signed char yytype_int8;
typedef yytype_int8 yy_state_t;
yet they don't show up in the buildfarm typedefs output. It's not a thing of
the binary, I checked that the symbols are present.
I have a hard time parsing the buildfarm code for generating the typedefs
file, tbh.
<stare>
Ah, I see. If I interpret that correctly, the code filters out symbols it
doesn't find in in some .[chly] file in the *source* directory. This code is,
uh, barely readable and massively underdocumented.
I guess I need to reimplement that :/. Don't immediately see how this could
be implemented for in-tree autoconf builds...
> > But in the attached patch I've implemented this slightly differently. If the
> > tooling to do so is available, the indent-* targets explained above,
> > use/depend on src/tools/pgindent/typedefs.list.merged (in the build dir),
> > which is the combination of a src/tools/pgindent/typedefs.list.local generated
> > for the local binaries/libraries and the source tree
> > src/tools/pgindent/typedefs.list.
>
> Hmm ... that allows indenting your C files, but how do you get from that
> to a non-noisy patch to commit to typedefs.list?
It doesn't provide that on its own. Being able to painlessly indent the files
seems pretty worthwhile already. But clearly it'd much better if we can
automatically update typedefs.list.
Greetings,
Andres Freund