From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: bokr@bokr.com
Cc: 73188@debbugs.gnu.org
Subject: bug#73188: PEG parser does not support full PEG grammar
Date: Mon, 23 Dec 2024 23:13:57 +0100 [thread overview]
Message-ID: <30f0bc78-51b7-4149-9943-d2550f531189@elenq.tech> (raw)
In-Reply-To: <Z2neZgp+6ZFTRV/0@BRL14v1>
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.
next prev parent reply other threads:[~2024-12-23 22:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 22:03 bug#73188: PEG parser does not support full PEG grammar Ekaitz Zarraga
2024-09-12 20:57 ` bug#73188: [PATCH v2] PEG: Add full support for PEG + some extensions Ekaitz Zarraga
2024-10-13 20:29 ` bug#73188: PEG parser does not support full PEG grammar Ludovic Courtès
2024-10-13 20:59 ` Ekaitz Zarraga
2024-10-14 11:56 ` Ludovic Courtès
2024-10-14 14:00 ` Ekaitz Zarraga
2024-10-20 10:10 ` Ludovic Courtès
2024-10-20 20:18 ` Ekaitz Zarraga
2024-12-09 17:23 ` Ludovic Courtès
2024-10-11 12:31 ` bug#73188: [PATCH] PEG: Add support for `not-in-range` and [^...] Ekaitz Zarraga
2024-10-30 19:04 ` bug#73188: PEG: Fix bugs and add complex PEG for testing Ekaitz Zarraga
2024-12-22 17:45 ` bug#73188: PEG parser does not support full PEG grammar Ekaitz Zarraga
2024-12-22 20:09 ` Ekaitz Zarraga
2024-12-22 20:01 ` bug#73188: [PATCH 1/3] PEG: fix [^...] Ekaitz Zarraga
2024-12-22 20:01 ` bug#73188: [PATCH 2/3] PEG: string-peg: better support for escaping Ekaitz Zarraga
2024-12-22 20:01 ` bug#73188: [PATCH 3/3] PEG: add large string-peg patch Ekaitz Zarraga
2024-12-22 21:22 ` bug#73188: PEG parser does not support full PEG grammar Ludovic Courtès
2024-12-23 22:04 ` bokr
2024-12-23 22:13 ` Ekaitz Zarraga [this message]
2024-12-28 20:30 ` Bengt Richter
2024-12-28 20:44 ` Ekaitz Zarraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30f0bc78-51b7-4149-9943-d2550f531189@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=73188@debbugs.gnu.org \
--cc=bokr@bokr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).