Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vcGGH-003kh5-2b for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Jan 2026 05:02:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vcGGF-00EWFP-28 for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Jan 2026 05:02:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vcGGF-00EWFG-1B for pgsql-hackers@lists.postgresql.org; Sun, 04 Jan 2026 05:02:40 +0000 Received: from mail-pj1-x1032.google.com ([2607:f8b0:4864:20::1032]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vcGGE-0045EG-2O for pgsql-hackers@lists.postgresql.org; Sun, 04 Jan 2026 05:02:39 +0000 Received: by mail-pj1-x1032.google.com with SMTP id 98e67ed59e1d1-34ab4879aa5so1254741a91.0 for ; Sat, 03 Jan 2026 21:02:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1767502957; x=1768107757; darn=lists.postgresql.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=3Qd+vaNvCrMWB7PS0fmAW2Hun2RwyTTYCHIkuLA4cnU=; b=hPx9+/3uM+MvOgrewWuJL2WC9BlPzsRLxz2K/5spIcmFrkuthq0fGavZRbcRCIv4Cj I2RoP1qVJ0VnIa1zYY1mrwBOBTjMKfNrZSg7z5uLKf8M+Tzx5rlEEyCsdamrpg8T6Md/ IaJrk43S0mcVMEiY3396qXvqeVja34n35iY7qSZuM1cqpJJIp1oLhF7Omc9WtOxsLmEf U59DUq1x3QyVZt0mk4fx+il/HhFAQ8dkQEHzpfRGc9z7Io4eDqpL48YOyCnHFUj+ionV xSoTGaBsuk+okpiyqoOs+3GwGFsDpb7uGRGvwP5EjidJ5ge40Mz/XO4EnZ/q4/PNXztN /gKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767502957; x=1768107757; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=3Qd+vaNvCrMWB7PS0fmAW2Hun2RwyTTYCHIkuLA4cnU=; b=awOTw6qrjltp9vlSvsxl2rUPkxcjUdTI/EJieqL3go3Op4Jrex4Lt/yVvQqnv+z4wq CqfIJX9YC2WDDDcZvZuZVmyMJBLR/0QrnjE+Ki9zVJCagcODXE/VtAFmFKO6oRcvHhim WAKXTPKRz1OfXHJq04t6gJZCdEmeLlXYnA7kKWAceGu5uB6dCe58HyIYdj2REB8eqLW3 esxpoAEIF+Ck/yhndE9XT+P90kQ6/n2eMBdxn+KpBWIDgPV67Yy0vsEMA72jQNs7xmCp e6btEIHeSFjZETS05E8Oo7lJNo/YF+bQXqbX9B7uW9CS+jVDa3QrF+R50UbCMKTc/0ma H4ow== X-Gm-Message-State: AOJu0Yy9UbolYzrs+g4leZ+DTq2pn+kjh2sWionQwZDRSM+X7GEqcvWM Ei0S/5a7czPyNOgEx20hpwySW2PrVuuO5vaxhivpHxQxWaueth05ngcaNBA89XCrLboQtKPOm2I zH5qCw9lCoXQ5DxGjU2XhDEAHq+0OBYxzfLUm X-Gm-Gg: AY/fxX5GEEJezD81kCfGuAulHXV8m+Wek54RGz8Rnru4tzpAPeSByg/QR/IlliRpcmD O+paKJ7znvnt5xR1mrg9ON/JDW0w9WrG0h4ItEsZc/UiPSZYzma0ws5B1OvWSWHImWZDD7nJleR O+ugldk7/fUW008cs4GmM+FBksM4sveNdygprYJc5hefLRSbxtNCxwY/CqiPvSFe9F19tThAc1Z z8F8PgvmzPRUd4UmsvSega4ZWKukVY8J05ZJ763j+OERX1vPV3NIgw1rAkuUULtq8qkRaBLdaLL 1EdjdyuIu6L2AGmI1PvvgqXECp5dFeP1jhpu2p1dbNfHUAAzi9Jr X-Google-Smtp-Source: AGHT+IHzvKOhFkZ0WAwdgxUf/QvlF3uOVkoSiL8c1Fj3FDAZqvsbOCN/6WvbH61d2JZqf5qhl0HsjJE97kp519d7ikM= X-Received: by 2002:a05:7300:d208:b0:2ae:5abf:ecff with SMTP id 5a478bee46e88-2b05ec6d589mr15218142eec.7.1767502956923; Sat, 03 Jan 2026 21:02:36 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Thomas Munro Date: Sun, 4 Jan 2026 18:02:00 +1300 X-Gm-Features: AQt7F2rfnwox_oLAri2IQfVz993bAlc3Gy5lxYFL4tthHW2GkEua4BEUAPzpKRg Message-ID: Subject: Re: LLVM 22 To: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Jan 3, 2026 at 3:02=E2=80=AFPM Thomas Munro wrote: > 1. We won't need our local llvm::backport::SectionMemoryManager for > LLVM 22, so it will be nice to draw a line under that messy business. > See commit message for details. While that's true, there is a problem with the patch I posted: "ReserveAlloc" is not enabled when called from C. I can't actually reproduce the issue locally due to lack of RAM connected to an ARM CPU, or I'd have noticed that... I'll attempt to do something about that upstream[1], let's see... if not, we can still use the new in-tree SectionMemoryManager, but we'll still need some C++ glue code. [1] https://github.com/llvm/llvm-project/issues/174305