From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Re: Bignum performance (was: Shrinking the C core) Date: Sat, 12 Aug 2023 18:22:45 +0200 Message-ID: <87y1igjkmi.fsf@dataswamp.org> References: <20230809094655.793FC18A4654@snark.thyrsus.com> <87il9owg0f.fsf@yahoo.com> <83fs4rjq9j.fsf@gnu.org> <87jzu2tvfc.fsf@dataswamp.org> <87y1ih3mc1.fsf@localhost> <87h6p5kcek.fsf@dataswamp.org> <87msyxoj2t.fsf@localhost> <875y5lkb4b.fsf@dataswamp.org> <87bkfdsmde.fsf@localhost> <87v8dlihc5.fsf@dataswamp.org> <87il9l1i59.fsf@localhost> <87pm3tgpts.fsf@dataswamp.org> <87y1ig3bog.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4846"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:zXIXZs1g9EWjCGXp8LJqJPCkPb4= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 12 18:58:49 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 1qUrwu-00015V-RG for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Aug 2023 18:58:48 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qUrwZ-0006eE-Eg; Sat, 12 Aug 2023 12:58:27 -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 1qUrOA-0007pI-IJ for emacs-devel@gnu.org; Sat, 12 Aug 2023 12:22:54 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qUrO8-0003YF-Rx for emacs-devel@gnu.org; Sat, 12 Aug 2023 12:22:54 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qUrO6-0008d6-UI for emacs-devel@gnu.org; Sat, 12 Aug 2023 18:22:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 12 Aug 2023 12:58:24 -0400 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:308620 Archived-At: Ihor Radchenko wrote: >> What one should do then is run it for 100 hours for 100 >> Emacs users' arbitrary Emacs use, then we would see what >> everyone was up to in the C part as well. > > There are known parts of Emacs C code that could see > performance optimization. But we need someone to actually go > ahead and provide patches. So to make Emacs faster, we need to: 1. Fix certain individual and identified areas in C that are currently slow for known reasons of the properties of the algorithms and/or data structure involved. 2. On a system level, find and change areas in C that have to do with how the Lisp model is implemented and upheld generally. 3. I don't know where the native/byte compiler would go from there, it it depends how big changes are in step 2. 4. Actual and existing Elisp code doesn't have to be changed a lot, and it would still be Elisp only it would be compiled with the methods from the CL world and in particular from SBCL. 5. This would not be a complete integration between Elisp and CL, but since the methods, tools and supply chain from CL would now be working for Elisp, it would be a big step towards such a possible integration in the future, if desired. -- underground experts united https://dataswamp.org/~incal