I wrote:
> * The autoconf build produces warnings about TOC overflow
> while linking the backend, as I showed upthread. I don't
> understand why -Wl,-bbigtoc doesn't silence that, especially
> since no such warnings appear in the meson build.
Hah, I've got at least part of the answer: that TOC warning appears
if the backend is built with -O0, but not at higher -O levels.
The apparent connection to autoconf vs. meson is because earlier
versions of the patch were building at -O0, due to template/aix
overriding CFLAGS and thereby preventing configure.ac from
inserting its default -O2. After I got rid of that interaction,
autoconf builds at -O2 by default and there's no warning.
Conversely, the warning does appear in the meson build if
I set -Dc_args=-O0.
Now, this is still a bit confusing, because the backend executable
is actually smaller at -O0 (due to less inlining, I guess), so
shouldn't it be less prone to TOC overflow? But I mainly cared
about the discrepancy between autoconf and meson builds,
and that seems adequately explained.
regards, tom lane
