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.94.2) (envelope-from ) id 1sm8jm-003X8b-1d for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Sep 2024 09:25:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sm8jk-006wpt-J2 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Sep 2024 09:25:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sm8jk-006wpl-8x for pgsql-hackers@lists.postgresql.org; Thu, 05 Sep 2024 09:25:08 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sm8ji-000GKZ-0e for pgsql-hackers@postgresql.org; Thu, 05 Sep 2024 09:25:08 +0000 Received: by mail-ot1-x332.google.com with SMTP id 46e09a7af769-70f660d2250so360772a34.2 for ; Thu, 05 Sep 2024 02:25:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725528304; x=1726133104; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Ilp2ooeIF9WYVS64tH4PW+3PHuKaV50frJf5BM2gxKA=; b=QwMiBlebe+DRFEa3YxfszZLcRC+bXGf7lBr9malshQ6vHBNQWLLWp2OMVzLObjQv2H pttvBhRrX03zG2I0rJTa2vUtYlP0LsIcuwUQQUZT/zM2wCM0iDKlIicg2t/XhScAXxhx 078S7zznRmXncJ9YpheVyC83+vAwQfQxjQKnCMm5WBDCKaCLMJMRxFWPW8tzqSDbyYf/ z9pUDInCHxtVzM3kysM/mjt8yectrOxUy5qCh7llT9rYOsy72v9nVTzG8TtkPar94uQb kNbQ4HrP9uTRWj/PjSP+oA52ivH2m+IrHCGhCaRuMeshRqlntaBZ0IP7QlXKcDhe3G2H dQXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725528304; x=1726133104; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Ilp2ooeIF9WYVS64tH4PW+3PHuKaV50frJf5BM2gxKA=; b=A20+3lSy/N1YVBclD5CdQXFbahHduxDoLNFnRY3cxK6ECus4TDU/7TDA4qc1eggYDq 5JLvY+aRYppkL6V1NdkCQei7vyzaNwoCQDl92Cn1Mc3/x3BVfA4dWkHVi8stIYulFZ/2 SKxdT0e3LmcWb2kDOsEHJ0a+Nnwhr5zWQkPCPaklUDs70BU8g0CF/isPoF/hsrSoFWAl 6xzPGVz5zf0y9OByOL19r998IQP8gNT3STesKc06I0vbXg8l0sk49fm4UrJ6cvndRgVN om4ASPh+8HwoXWP3bzQ1fhtcqlurr2IHAhzS6NIulC8ElWDtlkh69Sywy1h0iX0DI4L3 AmOQ== X-Gm-Message-State: AOJu0YxmpvPHddfmCrGRMTTr/tVrlOOnBNVujbYqm0mCiwGevjKsADnU ++0TX/oeJKZrzBlrmeH+uSYNrfyTYF1rHwNMtBolBOR/llprcajdSdSNoSxUXOYD2y7z4ltqlSQ uTdzQQkg4GFvIqDxvIvLlXZ8LNGApg+Tu X-Google-Smtp-Source: AGHT+IHn4lqPpOsscEoFex0peTBaJOOr0rd4ryKafUK/YKaZrFIotTjWwqT+WqPAFT5SyFMhNWOGTUCbnyn1FHW29g0= X-Received: by 2002:a05:6358:888:b0:1b5:fc3c:5520 with SMTP id e5c5f4694b2df-1b603c1401bmr2777228455d.7.1725528303704; Thu, 05 Sep 2024 02:25:03 -0700 (PDT) MIME-Version: 1.0 References: <206b001d-1884-4081-bd02-bed5c92f02ba@eisentraut.org> In-Reply-To: <206b001d-1884-4081-bd02-bed5c92f02ba@eisentraut.org> From: Nazir Bilal Yavuz Date: Thu, 5 Sep 2024 12:24:51 +0300 Message-ID: Subject: Re: meson vs. llvm bitcode files To: Peter Eisentraut Cc: pgsql-hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Thu, 5 Sept 2024 at 11:56, Peter Eisentraut wrote: > > The meson build currently does not produce llvm bitcode (.bc) files. > AFAIK, this is the last major regression for using meson for production > builds. > > Is anyone working on that? I vaguely recall that some in-progress code > was shared a couple of years ago, but I haven't seen anything since. It > would be great if we could collect any existing code and notes to maybe > get this moving again. I found that Andres shared a patch (v17-0021-meson-Add-LLVM-bitcode-emission.patch) a while ago [1]. [1] https://www.postgresql.org/message-id/20220927011951.j3h4o7n6bhf7dwau%40awork3.anarazel.de -- Regards, Nazir Bilal Yavuz Microsoft