pgsql: Use 4-byte slock_t on both PPC and PPC64. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Use 4-byte slock_t on both PPC and PPC64.
Date
Msg-id E1Rha2I-0007L6-7K@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Use 4-byte slock_t on both PPC and PPC64.

Previously we defined slock_t as 8 bytes on PPC64, but the TAS assembly
code uses word-wide operations regardless, so that the second word was
just wasted space.  There doesn't appear to be any performance benefit
in adding the second word, so get rid of it to simplify the code.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/8496c6cd77e2f5f105fc47315680174157d66647

Modified Files
--------------
src/include/storage/s_lock.h |    5 +----
1 files changed, 1 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Use mutex hint bit in PPC LWARX instructions, where possible.
Next
From: Bruce Momjian
Date:
Subject: pgsql: Add comment about skipping binary files for copyright changes.