From: lkcl <luke.leighton@gmail.com>
To: Dmitry Selyutin <ghostmansd@gmail.com>
Cc: Nick Alcock <nick.alcock@oracle.com>,
lkcl via Binutils <binutils@sourceware.org>
Subject: Re: Are big tests allowed in binutils?
Date: Tue, 21 Jun 2022 20:23:15 +0100 [thread overview]
Message-ID: <CAPweEDzvFPNyv=vndTWWJSgcwQL+QBmaGEY5QEqXZaS-MFHqzw@mail.gmail.com> (raw)
In-Reply-To: <CAMqzjets=G5BS6u_S5avzLwDK-MG-cGMGpifXbaUNJH9bhvYLQ@mail.gmail.com>
On Tue, Jun 21, 2022 at 6:30 PM Dmitry Selyutin <ghostmansd@gmail.com> wrote:
> On Tue, Jun 21, 2022 at 8:26 PM lkcl <luke.leighton@gmail.com> wrote:
> > describing where those tools are is a good call.
>
> ...as long as the tools _are_ available, which is not currently the
> case, since we still have to implement a good generator. Or did you
> mean the SVP64 source code itself by "tools"
sv_analysis [0], sv_binutils [1], and the [planned] test auto-generator.
whilst these tools are under the LGPLv3+ [2] and their output, because
they are effectively a compiler tool we *choose* to release the output
of those tools under the GPL [and assign it to the FSF] and one of the
dependencies is not GPL'd (BSD 2-clause) [3]
we have fully-automated install scripts for the installation of all
software dependencies. up to line 61 of this script [4] is sufficient.
where's a good place to include mention of that, should anyone else
wish to make modifications in future?
l.
[0] https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/sv/sv_analysis.py;hb=HEAD
[1] https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/sv/sv_binutils.py;hb=HEAD
[2] https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=COPYING.LGPLv3;hb=HEAD
[3] https://gitlab.com/nmigen/nmigen/-/blob/master/LICENSE.txt
[4] https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;hb=HEAD
next prev parent reply other threads:[~2022-06-21 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:11 Dmitry Selyutin
2022-06-17 6:19 ` Dmitry Selyutin
2022-06-20 10:42 ` Nick Alcock
2022-06-20 11:31 ` lkcl
2022-06-21 13:43 ` Nick Alcock
2022-06-21 17:26 ` lkcl
2022-06-21 17:29 ` Dmitry Selyutin
2022-06-21 19:23 ` lkcl [this message]
2022-06-17 9:14 ` Andreas Schwab
2022-06-21 15:32 ` Richard Earnshaw
2022-06-21 16:28 ` Dmitry Selyutin
2022-06-22 6:55 ` Jan Beulich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDzvFPNyv=vndTWWJSgcwQL+QBmaGEY5QEqXZaS-MFHqzw@mail.gmail.com' \
--to=luke.leighton@gmail.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@gmail.com \
--cc=nick.alcock@oracle.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).