From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Ideal performance of ELisp Date: Sun, 14 Aug 2022 09:01:39 -0400 Message-ID: References: <83mtceupbx.fsf@gnu.org> <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="35975"; 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: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 14 15:02:59 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 1oNDGc-0009CR-LV for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Aug 2022 15:02:58 +0200 Original-Received: from localhost ([::1]:34060 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oNDGb-0000KL-96 for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Aug 2022 09:02:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34370) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNDFT-0007JW-Up for emacs-devel@gnu.org; Sun, 14 Aug 2022 09:01:47 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:18034) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNDFR-0008Sb-C4; Sun, 14 Aug 2022 09:01:46 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id DF96E10013B; Sun, 14 Aug 2022 09:01:42 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 98B3B100121; Sun, 14 Aug 2022 09:01:41 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1660482101; bh=I5agXVnIziQYLwo/KVxaKy1Y5y5hd28CKK9JBQzpU1Q=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=QofiFd8L6VlGHCiJSBSRFOohZ4cuJ+VNc7i7odYONgIQa/iWi9JAiwJIF8XYLfuTS M/a68r8VV62RLZhCFyOBTWupyUAYmgy+BNdVj6k3zuv3/7Q4G0Q/rwT3p62yjn5E0p Fx5asAZB44HsUqObUHZKK6CngRJmb+ma+732OxCH3GDXbPfs/SrKqRdtD8l9RcmBXY l36OgrfA2PaYP+fCglg8SKMwjTc5wBVIl6AwlwFxOToUaKDzYIwz4UCRBbCsPbHLaG rNl1/SO8BZe5wrJ73QA8+BG4OioVjrfX1c+1GTxvXpuMUUA2ItZ+GMnn1Tc6GVUR2m nFNvutD6rPbyg== Original-Received: from pastel (unknown [45.72.195.111]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4F855120432; Sun, 14 Aug 2022 09:01:41 -0400 (EDT) In-Reply-To: (Andrea Corallo's message of "Sun, 14 Aug 2022 09:25:58 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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:293445 Archived-At: >>> 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. Stefan