2015-10-08 19:01:36 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* pg_bswap.h
|
|
|
|
* Byte swapping.
|
|
|
|
*
|
2017-09-30 00:52:55 +02:00
|
|
|
* Macros for reversing the byte order of 16, 32 and 64-bit unsigned integers.
|
2015-10-08 19:01:36 +02:00
|
|
|
* For example, 0xAABBCCDD becomes 0xDDCCBBAA. These are just wrappers for
|
|
|
|
* built-in functions provided by the compiler where support exists.
|
|
|
|
*
|
2017-09-30 00:52:55 +02:00
|
|
|
* Note that all of these functions accept unsigned integers as arguments and
|
|
|
|
* return the same. Use caution when using these wrapper macros with signed
|
|
|
|
* integers.
|
2015-10-08 19:01:36 +02:00
|
|
|
*
|
2017-01-03 19:48:53 +01:00
|
|
|
* Copyright (c) 2015-2017, PostgreSQL Global Development Group
|
2015-10-08 19:01:36 +02:00
|
|
|
*
|
|
|
|
* src/include/port/pg_bswap.h
|
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef PG_BSWAP_H
|
|
|
|
#define PG_BSWAP_H
|
|
|
|
|
2017-09-30 00:52:55 +02:00
|
|
|
|
|
|
|
/* In all supported versions msvc provides _byteswap_* functions in stdlib.h */
|
|
|
|
#ifdef _MSC_VER
|
|
|
|
#include <stdlib.h>
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
|
|
/* implementation of uint16 pg_bswap16(uint16) */
|
|
|
|
#if defined(HAVE__BUILTIN_BSWAP16)
|
|
|
|
|
|
|
|
#define pg_bswap16(x) __builtin_bswap16(x)
|
|
|
|
|
|
|
|
#elif defined(_MSC_VER)
|
|
|
|
|
|
|
|
#define pg_bswap16(x) _byteswap_ushort(x)
|
|
|
|
|
|
|
|
#else
|
|
|
|
|
|
|
|
static inline uint16
|
|
|
|
pg_bswap16(uint16 x)
|
|
|
|
{
|
|
|
|
return
|
|
|
|
((x << 8) & 0xff00) |
|
|
|
|
((x >> 8) & 0x00ff);
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif /* HAVE__BUILTIN_BSWAP16 */
|
|
|
|
|
|
|
|
|
|
|
|
/* implementation of uint32 pg_bswap32(uint32) */
|
|
|
|
#if defined(HAVE__BUILTIN_BSWAP32)
|
|
|
|
|
|
|
|
#define pg_bswap32(x) __builtin_bswap32(x)
|
|
|
|
|
|
|
|
#elif defined(_MSC_VER)
|
|
|
|
|
|
|
|
#define pg_bswap32(x) _byteswap_ulong(x)
|
|
|
|
|
2015-10-08 19:01:36 +02:00
|
|
|
#else
|
2017-09-30 00:52:55 +02:00
|
|
|
|
|
|
|
static inline uint32
|
|
|
|
pg_bswap32(uint32 x)
|
|
|
|
{
|
|
|
|
return
|
|
|
|
((x << 24) & 0xff000000) |
|
|
|
|
((x << 8) & 0x00ff0000) |
|
|
|
|
((x >> 8) & 0x0000ff00) |
|
|
|
|
((x >> 24) & 0x000000ff);
|
|
|
|
}
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* HAVE__BUILTIN_BSWAP32 */
|
2015-10-08 19:01:36 +02:00
|
|
|
|
2017-09-30 00:52:55 +02:00
|
|
|
|
|
|
|
/* implementation of uint64 pg_bswap64(uint64) */
|
|
|
|
#if defined(HAVE__BUILTIN_BSWAP64)
|
|
|
|
|
|
|
|
#define pg_bswap64(x) __builtin_bswap64(x)
|
|
|
|
|
|
|
|
|
|
|
|
#elif defined(_MSC_VER)
|
|
|
|
|
|
|
|
#define pg_bswap64(x) _byteswap_uint64(x)
|
|
|
|
|
2015-10-08 19:01:36 +02:00
|
|
|
#else
|
2017-09-30 00:52:55 +02:00
|
|
|
|
2017-09-30 02:41:20 +02:00
|
|
|
static inline uint64
|
|
|
|
pg_bswap64(uint64 x)
|
2017-09-30 00:52:55 +02:00
|
|
|
{
|
|
|
|
return
|
|
|
|
((x << 56) & UINT64CONST(0xff00000000000000)) |
|
|
|
|
((x << 40) & UINT64CONST(0x00ff000000000000)) |
|
|
|
|
((x << 24) & UINT64CONST(0x0000ff0000000000)) |
|
|
|
|
((x << 8) & UINT64CONST(0x000000ff00000000)) |
|
|
|
|
((x >> 8) & UINT64CONST(0x00000000ff000000)) |
|
|
|
|
((x >> 24) & UINT64CONST(0x0000000000ff0000)) |
|
|
|
|
((x >> 40) & UINT64CONST(0x000000000000ff00)) |
|
|
|
|
((x >> 56) & UINT64CONST(0x00000000000000ff));
|
|
|
|
}
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* HAVE__BUILTIN_BSWAP64 */
|
2015-10-09 21:06:06 +02:00
|
|
|
|
2017-09-30 00:52:55 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Portable and fast equivalents for for ntohs, ntohl, htons, htonl,
|
|
|
|
* additionally extended to 64 bits.
|
|
|
|
*/
|
|
|
|
#ifdef WORDS_BIGENDIAN
|
|
|
|
|
|
|
|
#define pg_hton16(x) (x)
|
|
|
|
#define pg_hton32(x) (x)
|
|
|
|
#define pg_hton64(x) (x)
|
|
|
|
|
|
|
|
#define pg_ntoh16(x) (x)
|
|
|
|
#define pg_ntoh32(x) (x)
|
|
|
|
#define pg_ntoh64(x) (x)
|
|
|
|
|
|
|
|
#else
|
|
|
|
|
|
|
|
#define pg_hton16(x) pg_bswap16(x)
|
|
|
|
#define pg_hton32(x) pg_bswap32(x)
|
|
|
|
#define pg_hton64(x) pg_bswap64(x)
|
|
|
|
|
|
|
|
#define pg_ntoh16(x) pg_bswap16(x)
|
|
|
|
#define pg_ntoh32(x) pg_bswap32(x)
|
|
|
|
#define pg_ntoh64(x) pg_bswap64(x)
|
|
|
|
|
|
|
|
#endif /* WORDS_BIGENDIAN */
|
|
|
|
|
|
|
|
|
2015-10-09 21:06:06 +02:00
|
|
|
/*
|
|
|
|
* Rearrange the bytes of a Datum from big-endian order into the native byte
|
|
|
|
* order. On big-endian machines, this does nothing at all. Note that the C
|
|
|
|
* type Datum is an unsigned integer type on all platforms.
|
|
|
|
*
|
|
|
|
* One possible application of the DatumBigEndianToNative() macro is to make
|
|
|
|
* bitwise comparisons cheaper. A simple 3-way comparison of Datums
|
|
|
|
* transformed by the macro (based on native, unsigned comparisons) will return
|
|
|
|
* the same result as a memcmp() of the corresponding original Datums, but can
|
|
|
|
* be much cheaper. It's generally safe to do this on big-endian systems
|
|
|
|
* without any special transformation occurring first.
|
|
|
|
*/
|
|
|
|
#ifdef WORDS_BIGENDIAN
|
|
|
|
#define DatumBigEndianToNative(x) (x)
|
|
|
|
#else /* !WORDS_BIGENDIAN */
|
|
|
|
#if SIZEOF_DATUM == 8
|
2017-09-30 00:52:55 +02:00
|
|
|
#define DatumBigEndianToNative(x) pg_bswap64(x)
|
2015-10-09 21:06:06 +02:00
|
|
|
#else /* SIZEOF_DATUM != 8 */
|
2017-09-30 00:52:55 +02:00
|
|
|
#define DatumBigEndianToNative(x) pg_bswap32(x)
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* SIZEOF_DATUM == 8 */
|
|
|
|
#endif /* WORDS_BIGENDIAN */
|
2015-10-08 19:01:36 +02:00
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* PG_BSWAP_H */
|