Package distribution method for RISC-V Sail model

[jjscheel]

Technical Group

Golden Model SIG

ratification-pkg

Technical Debt

Technical Liaison

Bill McSpadden

Task Category

SAIL model

Task Sub Category

• gcc
• binutils
• gdb
• intrinsics
• Java
• KVM
• ld
• llvm
• Linux kernel
• QEMU
• Spike

Ratification Target

3Q2023

Statement of Work (SOW)

Component names:
Sail

Requirements:
Currently, the RISC-V Sail model must be built (compiled) by the user. It has been requested that the model be compiled and distributed using industry-standard package management tools.

Deliverables:

1. A build a distribution method for the Sail model. Must include yum, apt and a package management for Windows and MacOS.
2. Documentation for the method.

Acceptance Criteria:

1. Accepted PRs into the Sail repo for all workflow activities
2. Packages that build, install on the target OSs, and pass the ACT test.

Projected timeframe: (best guess date)
6 person months

SOW Signoffs: (delete those not needed)

• Development partner sign-off
• Golden Model SIG sign-off

Waiver

• Freeze
• Ratification

Pull Request Details

No response

[lazyparser]

I am interested in accepting this task, and I think PLCT Lab's technical background can help. Since this week and next week are the Chinese New Year, I estimate that I can return some research results and plans around February 28 at the earliest.

[jjscheel]

@lazyparser and PLCT have expressed interest. I've also asked Greg Sterling to engage here too. I'll get him added to the issue as soon as I can.

[U2FsdGVkX1]

Fedora has already built all the dependencies and tested
please add this repo for testing
https://mirror.iscas.ac.cn/plct/distros/fedora/

[jjscheel]

Thanks for the information. @gsterlin, please take a look at this.

[yuzibo]

There are Debian packages about sail/sail-riscv and their dependent packages.
Source code is here.

Meanwhile, ocaml-linenoise, omd and lem has been pushed Debian salsa repo under Debian OCaml team and was waiting to sponsor them. Other packages are doing similar things.

[jrtc27]

Given how rapidly Sail is being modified at the moment to support new features for the model I’m not convinced having packages in Debian stable is at all useful. It seems highly likely that by the time they are released they won’t be usable.

[yuzibo]

Make sense.

If we want to use a fresh deb/rpm package, we would better to keep one final package, in other words, to keep sail-riscv package with an upstream distribution. But before this, these dependent packages should be packaged into distribution to reduce the maintenance burden.

[jjscheel]

@jrtc27, valid point.

@yuzibo, I agree that building packages now helps ensure that dependencies are available when Sail stabilizes.