postgresql/src/port
Tom Lane a7a7387575 Further improve code for probing the availability of ARM CRC instructions.
Andrew Gierth pointed out that commit 1c72ec6f4 would yield the wrong
answer on big-endian ARM systems, because the data being CRC'd would be
different.  To fix that, and avoid the rather unsightly hard-wired
constant, simply compare the hardware and software implementations'
results.

While we're at it, also log the resulting decision at DEBUG1, and error
out if the hw and sw results unexpectedly differ.  Also, since this
file must compile for both frontend and backend, avoid incorrect
dependencies on backend-only headers.

In passing, add a comment to postmaster.c about when the CRC function
pointer will get initialized.

Thomas Munro, based on complaints from Andrew Gierth and Tom Lane

Discussion: https://postgr.es/m/HE1PR0801MB1323D171938EABC04FFE7FA9E3110@HE1PR0801MB1323.eurprd08.prod.outlook.com
2018-05-03 11:32:57 -04:00
..
.gitignore
chklocale.c
crypt.c
dirent.c
dirmod.c
erand48.c
fls.c
fseeko.c
getaddrinfo.c
getopt_long.c
getopt.c
getpeereid.c
getrusage.c
gettimeofday.c
inet_aton.c
inet_net_ntop.c
isinf.c
kill.c
Makefile Fix partial-build problems introduced by having more generated headers. 2018-04-09 16:42:10 -04:00
mkdtemp.c
noblock.c
open.c
path.c
pg_crc32c_armv8_choose.c Further improve code for probing the availability of ARM CRC instructions. 2018-05-03 11:32:57 -04:00
pg_crc32c_armv8.c Preliminary work for pgindent run. 2018-04-26 14:45:04 -04:00
pg_crc32c_sb8.c
pg_crc32c_sse42_choose.c
pg_crc32c_sse42.c
pg_strong_random.c
pgcheckdir.c
pgmkdirp.c
pgsleep.c
pgstrcasecmp.c
pqsignal.c
pthread-win32.h
qsort_arg.c
qsort.c
quotes.c
random.c
README
rint.c
snprintf.c
sprompt.c
srandom.c
strerror.c
strlcat.c
strlcpy.c
strnlen.c
system.c
tar.c
thread.c
unsetenv.c
win32.ico
win32env.c
win32error.c
win32security.c
win32setlocale.c
win32ver.rc

src/port/README

libpgport
=========

libpgport must have special behavior.  It supplies functions to both
libraries and applications.  However, there are two complexities:

1)  Libraries need to use object files that are compiled with exactly
the same flags as the library.  libpgport might not use the same flags,
so it is necessary to recompile the object files for individual
libraries.  This is done by removing -lpgport from the link line:

        # Need to recompile any libpgport object files
        LIBS := $(filter-out -lpgport, $(LIBS))

and adding infrastructure to recompile the object files:

        OBJS= execute.o typename.o descriptor.o data.o error.o prepare.o memory.o \
                connect.o misc.o path.o exec.o \
                $(filter snprintf.o, $(LIBOBJS))

The problem is that there is no testing of which object files need to be
added, but missing functions usually show up when linking user
applications.

2) For applications, we use -lpgport before -lpq, so the static files
from libpgport are linked first.  This avoids having applications
dependent on symbols that are _used_ by libpq, but not intended to be
exported by libpq.  libpq's libpgport usage changes over time, so such a
dependency is a problem.  Windows, Linux, and macOS use an export list to
control the symbols exported by libpq.