From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Bengt Richter Newsgroups: gmane.lisp.guile.bugs Subject: bug#73188: PEG parser does not support full PEG grammar Date: Sat, 28 Dec 2024 12:30:32 -0800 Message-ID: References: <78a81bc5-cd0d-0506-185b-c733c66e96ae@elenq.tech> <20241222200128.13782-1-ekaitz@elenq.tech> <87seqffm66.fsf_-_@gnu.org> <30f0bc78-51b7-4149-9943-d2550f531189@elenq.tech> Reply-To: bokr@bokr.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13594"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 73188@debbugs.gnu.org To: Ekaitz Zarraga Original-X-From: bug-guile-bounces+guile-bugs=m.gmane-mx.org@gnu.org Sat Dec 28 21:31:36 2024 Return-path: Envelope-to: guile-bugs@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 1tRdTD-0003Om-3E for guile-bugs@m.gmane-mx.org; Sat, 28 Dec 2024 21:31:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tRdSq-0005RR-7p; Sat, 28 Dec 2024 15:31:12 -0500 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 1tRdSl-0005R5-20 for bug-guile@gnu.org; Sat, 28 Dec 2024 15:31:07 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tRdSh-0002E4-7o for bug-guile@gnu.org; Sat, 28 Dec 2024 15:31:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=In-Reply-To:MIME-Version:References:From:Date:To:Subject; bh=Il+p289GRbxCUATYgNenM+9Q0y0xlBMGKCL4d5M94po=; b=H72qf3QWxr4G2opw3fSpF8kOPXdcUJI0bLBMAkZeL4deY2tW8RBMuZrAKfkmaJBQ0J6N5CJY98VkUDHPmMrf7V7v0jO8SEpyOsdswHhkkIDZoaauQSzwPS5X9LgNgsqXJ7cIDcD9r1TgPxBbapHTmXWPESRkwtH2/QbkPBbXK4qoV/TYMPtTh+BmHD16Qzajw4HBEx4FE2Zd1WJjvIUfkE+7vMxWhTJjI0YsjfcEM2BBvqQpzAUC1sHnJZD7X6s5cEaPw0zL57bzXgCF7SSbhdkbhWSp6DECLBaAspJ54Fa+6eD+P5tKZY4xkA1Z5ve+iHkJ3OYUgTbWrvVl5YeV6w==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tRdSg-00084O-6u for bug-guile@gnu.org; Sat, 28 Dec 2024 15:31:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Bengt Richter Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Sat, 28 Dec 2024 20:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 73188 X-GNU-PR-Package: guile Original-Received: via spool by 73188-submit@debbugs.gnu.org id=B73188.173541785631009 (code B ref 73188); Sat, 28 Dec 2024 20:31:02 +0000 Original-Received: (at 73188) by debbugs.gnu.org; 28 Dec 2024 20:30:56 +0000 Original-Received: from localhost ([127.0.0.1]:52729 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tRdSa-000845-AV for submit@debbugs.gnu.org; Sat, 28 Dec 2024 15:30:56 -0500 Original-Received: from mailout.easymail.ca ([64.68.200.34]:35934) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tRdSW-00083q-V7 for 73188@debbugs.gnu.org; Sat, 28 Dec 2024 15:30:54 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id B980A60231; Sat, 28 Dec 2024 20:30:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1735417846; bh=3J50n7noPHSVvVhM5TlsED81m7VpcE6BkaXTBM7eND8=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=Iyj/bEElKYtsAr9gQBE8H05jwRXEsPxTKr3bxN6HFRinS40auXAvB3LHezwTPmmAg OHkL8DsFLjW/uVx0h94AS/o9XdEHkZ40npB0RYQ/HVRgtotPiGUSWDhr/MVFyrrKuS +BVf3VG6UpfQcUJ/qA9BojP2HqOSK4ERAKATB9vAwTVtpGNlLQipWRYi5Gd8DM9ILg pFudahcfs3Ja3BARxm7bsBFCg1y4AZM9OV9vT5WnP/9R4tFk7n1+1LLLW8DZPtzJm1 hbpmRCQPuFKBGn1kg3ebsSn0GsLSDWkYImeB4JAp4pFYzJ1elxVGEqjLUHb4eU4yS5 eUJx1+rGqkNtg== X-Virus-Scanned: Debian amavisd-new at emo07-pco.easydns.vpn Original-Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo07-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opu9HjiMUSbA; Sat, 28 Dec 2024 20:30:46 +0000 (UTC) Original-Received: from localhost (unknown [50.208.209.153]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id B12405FDF0; Sat, 28 Dec 2024 20:30:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1735417846; bh=3J50n7noPHSVvVhM5TlsED81m7VpcE6BkaXTBM7eND8=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=Iyj/bEElKYtsAr9gQBE8H05jwRXEsPxTKr3bxN6HFRinS40auXAvB3LHezwTPmmAg OHkL8DsFLjW/uVx0h94AS/o9XdEHkZ40npB0RYQ/HVRgtotPiGUSWDhr/MVFyrrKuS +BVf3VG6UpfQcUJ/qA9BojP2HqOSK4ERAKATB9vAwTVtpGNlLQipWRYi5Gd8DM9ILg pFudahcfs3Ja3BARxm7bsBFCg1y4AZM9OV9vT5WnP/9R4tFk7n1+1LLLW8DZPtzJm1 hbpmRCQPuFKBGn1kg3ebsSn0GsLSDWkYImeB4JAp4pFYzJ1elxVGEqjLUHb4eU4yS5 eUJx1+rGqkNtg== Content-Disposition: inline In-Reply-To: <30f0bc78-51b7-4149-9943-d2550f531189@elenq.tech> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane-mx.org@gnu.org Original-Sender: bug-guile-bounces+guile-bugs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.lisp.guile.bugs:11146 Archived-At: Hi Ekaitz and anyone interested, Sorry for misunderstandings ;-/ I thought you have made changes which make the MIT PEG standard [1] available in full, and I would like to use that full standard PEG syntax for defining something I have in mind. I realize that guile's underlying VM has a bytecode interpretation loop that is dynamically jit-optimized, and that this is orthogonal to whether the host system is RISCV or whatever, as far as using guile and guix as tools is concerned. (BTW UIAM you have contributed a lot to making this bug-free and clean, for which thanks! ) My interest in RISCV however is as a *target* output language for a compiler I'd like to define with PEG for transforming my peculiar DSL source to output RISCV source, then compile it to an image for execution by RISCV hardware or the quivalent qemu virtual hardware. I'd like to make a tool that can transform any source written in my peculiar ascii/utf8 DSL-syntax to a minimal self-contained bootable-in-RISCV-VM-or-HW ELF file. I can use the current PEG machinery for testing, but I'd like to avoid debugging things you have fixed :) Hence my interest in cloning your repo, so I can start using the MIT syntax [1] and be sure bugs I encounter will be *my* bugs and typos and design/coding mistakes ;-) Also, if I write do-what-i-want.scm using the peg accessible with guile3, the executable will not be a minimal ELF :) Thus my interest in the jit code would be to look for code snippets that I might be able to use for AHOT compilation. Probably someone is already working on something like that. (Anything I think of seems to be WIP somewhere on the internet already :) You write about committing your patches, so I was wondering what git repo you are committing into. I assume you have a private one on your laptop or otherwise near at hand, but are you pushing to some place that I could clone, and then use one of Ludo's magic pre-install incantations to access with use-module in a package definition of mine? BTW, re guix/guile development funding -- I am expecting ARM SOCs with RISCV cores to become important in the hacker/maker embedded world. Could guix/guile earn extra funding by having an investment coop llc that designs actual FLOSS HW/SW/FW and contracts to produce cool devices for profit? (Independent of FSF, and other benevolent sources, but allowing non-controlling investment from them). Sorry to hi-jack this thread. Please start a new one if interested in exploring anything here :) [1] -- Regards, Bengt Richter On +2024-12-23 23:13:57 +0100, Ekaitz Zarraga wrote: > Hi, > > > On 2024-12-23 23:04, bokr@bokr.com wrote: > > • Late kudos to Ekaitz for this great PEG contribution, especially RISCV, > > which will IMO play a key part in the future of human secure control over machines 🙂 > > I think I didn't understand your message very well, but just as a > clarification: the PEG work and RISC-V work are completely independent, one > doesn't have anything to do with the other, and the RISC-V work is not > merged in Guile yet. > > The RISC-V work for the Guile JIT (guile already works in riscv without it) > is in here: > https://gitlab.com/wingo/lightening/-/merge_requests/14 > > Hope this clarifies things.