From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Native compilation on as default? Date: Thu, 26 Oct 2023 09:39:39 +0300 Message-ID: <83y1fphopg.fsf@gnu.org> References: <83legs281v.fsf@gnu.org> <83r0liiy44.fsf@gnu.org> <874jie1avt.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21737"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, acorallo@gnu.org, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 26 08:40:27 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvu2c-0005Wo-My for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Oct 2023 08:40:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvu1n-0006vl-AU; Thu, 26 Oct 2023 02:39:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvu1k-0006vX-VG for emacs-devel@gnu.org; Thu, 26 Oct 2023 02:39:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvu1j-0005Cv-3A; Thu, 26 Oct 2023 02:39:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=WRHhgP4LfHVFllZMVomKOTEDvQTf64mpcd0VoSMWAI0=; b=DgghG1LP2inx Q5uz6xDFuDnujiOEMOT0RsSpV2XY22fP5jrx54LVpQNjd6KmeSrBPYGPhYkiDsQ94/kqPdBQN//pN LMGaQRxdKGXoHbbizouPhMiBMKJR0jhZElYCkIuPt+Ky/Y/x3L8hIG4goOMMWQixngAg0HsOy/9lM fkeiPZ9Y3Wd8se6b/0WbYu1pcsw2o2yBIBvWNUFGGKOcX3K1KFsgBA3HWb8SjWc86YVh35UxTrI3M DYIw+F2hpiMJpon/W+q8+RjByswsQKEGAA+I9EBPrvwNpBzJp2N55NN+G6HllY/KGJ9i2sBD8mgvi VuW/V5H+xOckoDsFmvfbFg==; In-Reply-To: <874jie1avt.fsf@yahoo.com> (message from Po Lu on Thu, 26 Oct 2023 08:32:38 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311883 Archived-At: > From: Po Lu > Cc: Andrea Corallo , Eli Zaretskii , > emacs-devel@gnu.org > Date: Thu, 26 Oct 2023 08:32:38 +0800 > > I'm not opposed to this in principle, but two precautions are > prerequisite for instituting such a change. First, the configure script > must arrange for native compilation to be disabled if libgccjit is > unavailable (or else ./configure && make will no longer work) That goes without saying: we cannot possibly fail a build because a silly default, can we? > and second, I think it should be disabled when building from the Git > repository, for native compilation delays making the Lisp directory > by a length of time that is unacceptable for Emacs development. People who work on Emacs development can easily disable native compilation at configure time, so I don't see any reason to treat a build from Git specially. (Also, the fact that someone builds from Git doesn't necessarily mean he or she is an Emacs developer, not at all.) So I think if we decide to make the native-compiling config the default when libgccjit is available, we could do that as we do with any other yes-if-available options.