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 1rk2L3-009ode-7x for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Mar 2024 13:38:41 +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 1rk2L1-00CoMj-He for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Mar 2024 13:38: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.94.2) (envelope-from ) id 1rk2L1-00CoMb-8U for pgsql-hackers@lists.postgresql.org; Tue, 12 Mar 2024 13:38:39 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rk2Ky-0047kQ-9U for pgsql-hackers@postgresql.org; Tue, 12 Mar 2024 13:38:38 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2d309a23d76so55960941fa.1 for ; Tue, 12 Mar 2024 06:38:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710250715; x=1710855515; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=MIdf0drtl9i6Ctaj5unP/y4d2C6jQfxRUlsR/ADBD6Y=; b=baWR72+Gz5Y6CfZ7nknCu94be/MkT4nXRYtk+c6GiU6rZ+nF7o0qNCsvzNSfK9EXR6 Gd+g4m+WJb+mAz3ltBLtZnmbB823DaeFaDWlMwQWWZKdYUJSnffSyeGc/qahHtcpr5Ru PSXpn3lYYSaN6A2j1LUQttcN3H+l4+VWJ4ooOujCkjNKzhHADbYtE2hUD2uKUL83UIQo 9CfsYOWfLjsqB0tSTxkpe8UDa0sadruGlwkTsbJ+seE8nsTYVSTGyFssbKZ0gSgr8laE u/jVMa8+Cg3+VmiT5Mk9QPPbx+NhK+Pn01EZ3fkp8AFl+LAQU3Vlk5SPMRApBGT/cyL4 NTCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710250715; x=1710855515; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MIdf0drtl9i6Ctaj5unP/y4d2C6jQfxRUlsR/ADBD6Y=; b=VziDKNtM0YXgGzGvLq0XQXiycgQQXSeSEVsdsl2HLmWMkxqqZtkeE5EzlrJtkrN+ca 7RM9EtkG+Gg/XdGBlcDAvGzuRE8Mcfq/BMjJULvSyaNN4Igw2cT+irkWDCszbclWp/nM guJF9Q7gz6olkZZVdl6qODDJ7fAUCsoBZhuDA99cPf66NjKsJBqb9ePOW5Q3EKyS3sOU C9rP0gm/WceWEl/00v4eNGpzx8KifyYtp2o4xeZpBJlHYOEWhecuAj8+FxoUeVzPGObQ EOfmcHqeZ3IFX7QzlRsRSB0+JcAD3ns7/ZuqYXqNLdmMvVgMvpGLlvzpOicU4Y26xKn0 UeEw== X-Gm-Message-State: AOJu0YzY8TUuSVbWap5pdbG2VzGDHtFnMVuorNjdp8hv5bjsQuWv3VQQ czhrE3W/wWWOX1bwXg9jgKieALXE7uMxqkB7NMlcZqWx0IiRlDyKQqAeZwf3FWzCl7xE/N2FMMg isFfquqffk3kJar9pADNst72WqtFZXLeiyRLkYC/B X-Google-Smtp-Source: AGHT+IHY3ctKo9txkspXl4B2zNot/csl/7WeLECNcZKEoGjdOMTkzr8Wv5Djm6YVnPfoDsrSu8sKod3VuMn0zfJQQ0s= X-Received: by 2002:a2e:9006:0:b0:2d4:26c0:5731 with SMTP id h6-20020a2e9006000000b002d426c05731mr3338939ljg.26.1710250715201; Tue, 12 Mar 2024 06:38:35 -0700 (PDT) MIME-Version: 1.0 From: Xing Guo Date: Tue, 12 Mar 2024 21:38:23 +0800 Message-ID: Subject: Disable LLVM bitcode generation with pgxs.mk framework. To: 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 hackers, When the PostgreSQL server is configured with --with-llvm, the pgxs.mk framework will generate LLVM bitcode for extensions automatically. Sometimes, I don't want to generate bitcode for some extensions. I can turn off this feature by specifying with_llvm=0 in the make command. ``` make with_llvm=0 ``` Would it be possible to add a new switch in the pgxs.mk framework to allow users to disable this feature? E.g., the Makefile looks like: ``` WITH_LLVM=no PG_CONFIG = pg_config PGXS := $(shell $(PG_CONFIG) --pgxs) ``` Best Regards, Xing