From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Native compilation on Windows, was Re: Bootstrap Compilation Speed Date: Mon, 17 Jan 2022 09:34:27 +0000 Message-ID: References: <86wnj18f7w.fsf@duenenhof-wilhelm.de> <65b2a18bc1a597333b42d35a2717dc33@russet.org.uk> <86lezg95ud.fsf_-_@duenenhof-wilhelm.de> <83a6fwysb3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38592"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st, emacs-devel@gnu.org, phillip.lord@russet.org.uk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 17 10:43:16 2022 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 1n9OXj-0009mF-NF for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Jan 2022 10:43:15 +0100 Original-Received: from localhost ([::1]:54682 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9OXi-0002Kh-Dq for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Jan 2022 04:43:14 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48022) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9OVn-00089H-9i for emacs-devel@gnu.org; Mon, 17 Jan 2022 04:41:15 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:62228) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9OVh-0006wn-CQ for emacs-devel@gnu.org; Mon, 17 Jan 2022 04:41:10 -0500 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 20H9YRYW014527 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 17 Jan 2022 09:34:28 GMT In-Reply-To: <83a6fwysb3.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 Jan 2022 10:54:08 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action 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" Xref: news.gmane.io gmane.emacs.devel:284867 Archived-At: Eli Zaretskii writes: >> Date: Sat, 15 Jan 2022 22:14:56 +0000 >> From: phillip.lord@russet.org.uk >> Cc: Corwin Brust , Emacs developers >> >> The problem is that native comp needs libgccjit at compile time but >> also at runtime. To make an executable install package like we have >> at the moment essentially means packaging libgccjit. Which means gcc >> and half of the msys2 toolchain. > > We made a point of implementing native-compilation on MS-Windows in a > way that doesn't require such extreme measures. Emacs built with > native-compilation support should be able to run on a Windows system > without GCC and Binutils installed, it just won't be able to > natively-compile any new or modified Lisp files. It will use the > *.elc files instead. > > Or at least that is the theory. Agree, before we rely on this behavior would be nice if someone could test it tho. Best Regards Andrea