| From: | "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change copyObject() to use typeof_unqual |
| Date: | 2026-03-17 10:56:24 |
| Message-ID: | DH504CLRFOBW.3FKN0ZDCG3U1S@jeltef.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Hardcode-typeof_unqual-to-__typeof_unqual__-for-c.patch | text/x-patch | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-03-17 11:01:43 | Re: Skipping schema changes in publication |
| Previous Message | Antonin Houska | 2026-03-17 10:53:40 | Re: Adding REPACK [concurrently] |