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.help Subject: Re: limit native compilation - how Date: Tue, 18 Jan 2022 16:34:04 +0200 Message-ID: <83mtjtun8j.fsf@gnu.org> References: <8735lp57kl.fsf@yandex.com> <83r199ymxj.fsf@gnu.org> <875yqluem4.fsf@zoho.eu> <83pmoszxwx.fsf@gnu.org> <874k64ddwo.fsf@yandex.com> <86h7a4954a.fsf@duenenhof-wilhelm.de> <83czksyszr.fsf@gnu.org> <86zgnv7w9n.fsf@duenenhof-wilhelm.de> <83wnizykig.fsf@gnu.org> <86r1977uu6.fsf@duenenhof-wilhelm.de> <83tue3yiw9.fsf@gnu.org> <86h7a37qzf.fsf@duenenhof-wilhelm.de> <87zgnvdcpw.fsf@zoho.eu> <86czkr7pov.fsf@duenenhof-wilhelm.de> <83o84bye6m.fsf@gnu.org> <86y23f5xxd.fsf@duenenhof-wilhelm.de> <83zgnvwmc1.fsf@gnu.org> <86tue25vo9.fsf@duenenhof-wilhelm.de> <83fspmwjym.fsf@gnu.org> <86pmoq5omh.fsf@duenenhof-wilhelm.de> <868rve5gmc.fsf@duenenhof-wilhelm.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13759"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 18 16:51:28 2022 Return-path: Envelope-to: geh-help-gnu-emacs@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 1n9qla-0003Ne-Mm for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 18 Jan 2022 16:51:26 +0100 Original-Received: from localhost ([::1]:57604 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9qlZ-0003q5-Po for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 18 Jan 2022 10:51:25 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59030) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9pYq-0004OE-Og for help-gnu-emacs@gnu.org; Tue, 18 Jan 2022 09:34:14 -0500 Original-Received: from [2001:470:142:3::e] (port=36770 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9pYq-0008RE-FC for help-gnu-emacs@gnu.org; Tue, 18 Jan 2022 09:34:12 -0500 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=0zW7wkFr4Qd3M0c+e+BPjwbVZZYN8EO0QyGNfqAbc7U=; b=FymOLyUmZ8Fj SGatEj76Vf7x7GMUYg90QQ4zYZwey952paYztEovdN1QujGuPn+iX/inAIM9ygxNMqIioe6hnrI1G 32HaO7720mQC7GmHElgKZkd6ATWT+bObvzubQ5veFerwfGogjYBIiXq5hKu8l/dhl0ngHfjIx80GN iaKgetkYUd1gOcu7M0JzXrEYDNR5vjBtA3bKDdvAduzoRf+LRfExoK9eYcHCTdHiPKRNYyxoE15qr YNbXnj/y95G+Lj+4y3ek1KNziULAMf09xXDAyuPxonNxhN4rNvqOWAMdvh3ju+lxiznto+V9MEKGP qI6vo1chinteK3FgJ5erAw==; Original-Received: from [87.69.77.57] (port=1521 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9pYq-0000eV-2j for help-gnu-emacs@gnu.org; Tue, 18 Jan 2022 09:34:12 -0500 In-Reply-To: (message from Corwin Brust on Mon, 17 Jan 2022 15:54:55 -0600) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135427 Archived-At: > From: Corwin Brust > Date: Mon, 17 Jan 2022 15:54:55 -0600 > Cc: Eli Zaretskii , Help Gnu Emacs mailing list > > I don't know if it is it safe to simply include the native-lisp folder > or if this would causes issues for Windows users who do have libgccjib > but don't have the same CPU as I do. (Locally I have: Intel(R) > Core(TM) i7-6950X CPU @ 3.00GHz 3.00 GHz) I don't know if the eln > files are CPU/arch-specific or if this should work fine for (e.g.) i9, > AMD chips, those with newer chipsets than my x99, and so forth. This is not about the CPU you have, this is about the CPU-specific code-tuning options you pass to libgccjit when you natively-compile the *.el files. Since I find it hard to believe you tweaked native-comp-compiler-options to pass non-default options to the compiler, the resulting code should be generic enough to run on any 64-bit machine running Windows (if you build for x86_64) or on any machine running any version of Windows if you build for x86. Again, this is the theory. But here we have at leas partial proof from the fact that Emacs itself runs on all those other systems, since emacs.exe is compiled and linked by the same utilities used to produce the *.eln files.