Re: Change copyObject() to use typeof_unqual - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Change copyObject() to use typeof_unqual
Date
Msg-id 0b2c3f99-b27a-4921-9271-33ab1bd231a3@eisentraut.org
Whole thread Raw
In response to Re: Change copyObject() to use typeof_unqual  ("Jelte Fennema-Nio" <postgres@jeltef.nl>)
List pgsql-hackers
On 17.03.26 11:56, Jelte Fennema-Nio wrote:
> On Tue Mar 17, 2026 at 3:39 AM CET, Tom Lane wrote:
>> While this version of clang doesn't like typeof_unqual, it does take
>> __typeof_unqual__.  So maybe we were premature to decide that we
>> could prefer the typeof_unqual spelling.
> 
> Hmmm, that makes sense. How about this patch to at least keep the
> all the logic related to this in one place? I was able to reproduce this
> error using the following flags, and this fixes the issue for me.
> 
> CC=clang-21 CXX=clang++-21 CFLAGS=-std=c23 BITCODE_CFLAGS=-std=gnu17 
> CLANG=clang-19 LLVM_CONFIG=llvm-config-19

committed




pgsql-hackers by date:

Previous
From: "Greg Burd"
Date:
Subject: Re: Expanding HOT updates for expression and partial indexes
Next
From: Robert Haas
Date:
Subject: Re: Why clearing the VM doesn't require registering vm buffer in wal record