Re: Use -fvisibility=hidden for shared libraries
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-hackers@postgresql.org
Date: 2022-07-27T18:02:28Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2022-07-18 00:05:16 -0700, Andres Freund wrote: >> Given that that's just about all compilers we support using configure, perhaps >> we should just move that out of the compiler specific section? Doesn't look >> like there's much precedent for that so far... > Here's a potential patch along those lines. Now that the dust from the main patch is pretty well settled, +1 for trying that. > I wonder if we also should move the -fno-strict-aliasing, -fwrapv tests > out. But that'd be something for later. Those seem less likely to be portable to non-gcc-alike compilers. On the other hand, maybe it'd be interesting to just remove the conditionality temporarily and try ALL the switches on all compilers, just to see what we can learn from the buildfarm. regards, tom lane
Commits
-
Mark all symbols exported from extension libraries PGDLLEXPORT.
- 8cf64d35eacc 16.0 landed
-
Default to hidden visibility for extension libraries where possible
- 089480c07705 16.0 landed
-
Remove now superfluous declarations of dlsym()ed symbols.
- fd4bad165539 16.0 landed
-
Add central declarations for dlsym()ed symbols
- f2b73c8d75d5 16.0 landed