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: Ideal performance of ELisp Date: Tue, 16 Aug 2022 08:59:01 +0000 Message-ID: References: <83lerxvfnu.fsf@gnu.org> <838rnxvdcq.fsf@gnu.org> <83r11ptksn.fsf@gnu.org> <83a68dti6w.fsf@gnu.org> <874jykzvx9.fsf@yahoo.com> <83fsi4sttn.fsf@gnu.org> <838rnws5c7.fsf@gnu.org> <838rntocb8.fsf@gnu.org> <875yiw92p2.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="8485"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Ihor Radchenko , Eli Zaretskii , Lynn Winebarger , luangruo@yahoo.com, acm@muc.de, emacs-devel@gnu.org, casouri@gmail.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 16 11:00:54 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 1oNsRR-00020K-1o for ged-emacs-devel@m.gmane-mx.org; Tue, 16 Aug 2022 11:00:53 +0200 Original-Received: from localhost ([::1]:51048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oNsRP-0001Q9-Qj for ged-emacs-devel@m.gmane-mx.org; Tue, 16 Aug 2022 05:00:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55968) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNsPt-0000iQ-I8 for emacs-devel@gnu.org; Tue, 16 Aug 2022 04:59:18 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:60933) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNsPr-0008KG-9Y; Tue, 16 Aug 2022 04:59:16 -0400 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 27G8x1Ie003561 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 16 Aug 2022 08:59:02 GMT In-Reply-To: (Stefan Monnier's message of "Sun, 14 Aug 2022 09:01:39 -0400") 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, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:293493 Archived-At: Stefan Monnier writes: >>>> Could it be possible to embed C snippets into lisp functions directly? >>>> Similar to assembler snippets in C. >>> >>> Andrea is better placed to answer that, but I think it would be fairly >>> easy to allow insertion of "C-like" snippets when the code gets compiled >>> with the native compiler. >>> >>> Of course, we'd probably want to make it work even when the code is >>> interpreted (or only compiled to bytecode). >>> >>> It would probably offer very handy improvements to the module API. >> >> I think the main issue is that libgccjit does not compile C but >> libgccir. I can't think of a nice way to blend the two things as of >> now. > > I was thinking of a C-like DSL (probably with a Lisp-style syntax). > Designed to be easy to translate to libgccir as well as not too hard > to interpret when libgccjit is not available. Yep that's an option, I thought about that as well, not sure how much practical it is tho. One of the downside is that we could not consume nor provide any of the existing C header files. Andrea