1996-10-27 10:55:05 +01:00
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
|
#
|
|
|
|
|
# Makefile--
|
|
|
|
|
# Makefile for storage/lmgr
|
|
|
|
|
#
|
|
|
|
|
# IDENTIFICATION
|
2010-09-20 22:08:53 +02:00
|
|
|
# src/backend/storage/lmgr/Makefile
|
1996-10-27 10:55:05 +01:00
|
|
|
#
|
|
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
|
|
2000-08-31 18:12:35 +02:00
|
|
|
subdir = src/backend/storage/lmgr
|
|
|
|
|
top_builddir = ../../../..
|
|
|
|
|
include $(top_builddir)/src/Makefile.global
|
1996-10-27 10:55:05 +01:00
|
|
|
|
2019-11-05 23:41:07 +01:00
|
|
|
OBJS = \
|
|
|
|
|
condition_variable.o \
|
|
|
|
|
deadlock.o \
|
|
|
|
|
lmgr.o \
|
|
|
|
|
lock.o \
|
|
|
|
|
lwlock.o \
|
|
|
|
|
lwlocknames.o \
|
|
|
|
|
predicate.o \
|
|
|
|
|
proc.o \
|
|
|
|
|
s_lock.o \
|
|
|
|
|
spin.o
|
1996-10-27 10:55:05 +01:00
|
|
|
|
2008-02-19 11:30:09 +01:00
|
|
|
include $(top_srcdir)/src/backend/common.mk
|
1996-10-27 10:55:05 +01:00
|
|
|
|
2006-04-29 00:54:31 +02:00
|
|
|
ifdef TAS
|
|
|
|
|
TASPATH = $(top_builddir)/src/backend/port/tas.o
|
|
|
|
|
endif
|
|
|
|
|
|
Replace random(), pg_erand48(), etc with a better PRNG API and algorithm.
Standardize on xoroshiro128** as our basic PRNG algorithm, eliminating
a bunch of platform dependencies as well as fundamentally-obsolete PRNG
code. In addition, this API replacement will ease replacing the
algorithm again in future, should that become necessary.
xoroshiro128** is a few percent slower than the drand48 family,
but it can produce full-width 64-bit random values not only 48-bit,
and it should be much more trustworthy. It's likely to be noticeably
faster than the platform's random(), depending on which platform you
are thinking about; and we can have non-global state vectors easily,
unlike with random(). It is not cryptographically strong, but neither
are the functions it replaces.
Fabien Coelho, reviewed by Dean Rasheed, Aleksander Alekseev, and myself
Discussion: https://postgr.es/m/alpine.DEB.2.22.394.2105241211230.165418@pseudo
2021-11-29 03:32:36 +01:00
|
|
|
s_lock_test: s_lock.c $(top_builddir)/src/common/libpgcommon.a $(top_builddir)/src/port/libpgport.a
|
2004-10-07 02:08:04 +02:00
|
|
|
$(CC) $(CPPFLAGS) $(CFLAGS) -DS_LOCK_TEST=1 $(srcdir)/s_lock.c \
|
Replace random(), pg_erand48(), etc with a better PRNG API and algorithm.
Standardize on xoroshiro128** as our basic PRNG algorithm, eliminating
a bunch of platform dependencies as well as fundamentally-obsolete PRNG
code. In addition, this API replacement will ease replacing the
algorithm again in future, should that become necessary.
xoroshiro128** is a few percent slower than the drand48 family,
but it can produce full-width 64-bit random values not only 48-bit,
and it should be much more trustworthy. It's likely to be noticeably
faster than the platform's random(), depending on which platform you
are thinking about; and we can have non-global state vectors easily,
unlike with random(). It is not cryptographically strong, but neither
are the functions it replaces.
Fabien Coelho, reviewed by Dean Rasheed, Aleksander Alekseev, and myself
Discussion: https://postgr.es/m/alpine.DEB.2.22.394.2105241211230.165418@pseudo
2021-11-29 03:32:36 +01:00
|
|
|
$(TASPATH) -L $(top_builddir)/src/common -lpgcommon \
|
|
|
|
|
-L $(top_builddir)/src/port -lpgport -o s_lock_test
|
2004-06-19 21:43:11 +02:00
|
|
|
|
Fix make rules that generate multiple output files.
For years, our makefiles have correctly observed that "there is no correct
way to write a rule that generates two files". However, what we did is to
provide empty rules that "generate" the secondary output files from the
primary one, and that's not right either. Depending on the details of
the creating process, the primary file might end up timestamped later than
one or more secondary files, causing subsequent make runs to consider the
secondary file(s) out of date. That's harmless in a plain build, since
make will just re-execute the empty rule and nothing happens. But it's
fatal in a VPATH build, since make will expect the secondary file to be
rebuilt in the build directory. This would manifest as "file not found"
failures during VPATH builds from tarballs, if we were ever unlucky enough
to ship a tarball with apparently out-of-date secondary files. (It's not
clear whether that has ever actually happened, but it definitely could.)
To ensure that secondary output files have timestamps >= their primary's,
change our makefile convention to be that we provide a "touch $@" action
not an empty rule. Also, make sure that this rule actually gets invoked
during a distprep run, else the hazard remains.
It's been like this a long time, so back-patch to all supported branches.
In HEAD, I skipped the changes in src/backend/catalog/Makefile, because
those rules are due to get replaced soon in the bootstrap data format
patch, and there seems no need to create a merge issue for that patch.
If for some reason we fail to land that patch in v11, we'll need to
back-fill the changes in that one makefile from v10.
Discussion: https://postgr.es/m/18556.1521668179@sss.pgh.pa.us
2018-03-23 18:45:37 +01:00
|
|
|
# see notes in src/backend/parser/Makefile
|
|
|
|
|
lwlocknames.c: lwlocknames.h
|
|
|
|
|
touch $@
|
2015-09-11 19:58:28 +02:00
|
|
|
|
|
|
|
|
lwlocknames.h: $(top_srcdir)/src/backend/storage/lmgr/lwlocknames.txt generate-lwlocknames.pl
|
|
|
|
|
$(PERL) $(srcdir)/generate-lwlocknames.pl $<
|
|
|
|
|
|
2004-06-19 21:43:11 +02:00
|
|
|
check: s_lock_test
|
2001-09-27 21:10:02 +02:00
|
|
|
./s_lock_test
|
|
|
|
|
|
2015-09-11 19:58:28 +02:00
|
|
|
clean distclean:
|
2008-02-19 11:30:09 +01:00
|
|
|
rm -f s_lock_test
|
2015-09-11 19:58:28 +02:00
|
|
|
|
|
|
|
|
maintainer-clean: clean
|
|
|
|
|
rm -f lwlocknames.h lwlocknames.c
|
