postgres.git / summary / log / commit / refs

commit    f89a5c086f8a2837ee122b3e3631f0b41a3a7865
Author:   Peter Eisentraut <peter@eisentraut.org>
Date:     Wed Sep 23 07:16:33 2026 +0000

    Fix alignas placement in GinTuple
    
    Commit 05c4b10fc52 added an alignas specifier, and placed it in the
    middle of the declaration, unlike most existing uses, possibly to
    avoid the indentation problem recently fixed in commit 884f82ae262.
    This placement is valid in C but not in C++, which requires it to be
    at the beginning.  This results in a warning in g++ and an error in
    clang++.  Fix by moving it accordingly.  The fix for the indentation
    problem has been backpatched to support this patch.


 src/include/access/gin_tuple.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/include/access/gin_tuple.h b/src/include/access/gin_tuple.h
index d2c7b50d1de..e918946f213 100644
--- a/src/include/access/gin_tuple.h
+++ b/src/include/access/gin_tuple.h
@@ -33,7 +33,7 @@ typedef struct GinTuple
 	 * The key value is accessed in place, so it must be aligned well enough
 	 * for any key type.
 	 */
-	char		alignas(MAXIMUM_ALIGNOF) data[FLEXIBLE_ARRAY_MEMBER];
+	alignas(MAXIMUM_ALIGNOF) char data[FLEXIBLE_ARRAY_MEMBER];
 } GinTuple;
 
 static inline ItemPointer


[parent: c81972f36593]