Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHqZLUWsJ-m2EDJdpfWb0AaQJ2zw-o4TJfJ70CWS6pfQQDLBEQ@mail.gmail.com>
Date: Wed, 3 Jun 2026 10:24:56 +0100
From: Walid Trabelsi <walid.tr@...il.com>
To: musl@...ts.openwall.com
Subject: Question: origin/version of TRE code in musl regex

Hello musl maintainers,

I am currently analyzing the origin and versioning of the regex
implementation used in musl libc (specifically musl 1.1.24) for open source
compliance purposes.
>From my investigation, I understand that musl incorporates code derived
from the TRE (Tagged Regular Expressions) project by Ville Laurikari, and
that this code was initially imported around February 2011.

Based on available evidence:
- The latest upstream TRE release prior to that time appears to be v0.8.0
(2009)
- The musl source references TRE copyright (2001–2009)
- The regex engine structure (TNFA, tag handling, etc.) aligns with TRE
design

However, it is unclear whether the imported code corresponds exactly to a
specific upstream TRE release (such as v0.8.0), or if it was based on a
snapshot or modified version at the time of import.

Could you please clarify:

1. Was the TRE code in musl originally imported from a specific released
version (e.g., v0.8.0), or from a development snapshot?
2. Is there any known mapping or reference commit in the TRE project that
corresponds to the imported code?
3. Is it correct to describe musl’s regex implementation as a fork derived
from TRE v0.8.0, subsequently modified and maintained independently?

Any clarification would be greatly appreciated, as it will help ensure
accurate attribution and documentation.

Thank you for your time and for maintaining musl.

Best regards,

*Walid TRABELSI*
*Ingénieur étude & développement systèmes embarqués*

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.