CI: Support publish prebuilt binaries for different platforms.

Open
#3 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start by reviewing the repository's CI and release configuration, using the v0.16.2 QuickJS release as the reference point. Define the supported platforms and verify that each produces a publishable prebuilt binary that can be used by the quickjs-oxide tests and benchmark workflow.

Written by the indexing model from the issue text.

Description

https://github.com/quickjs-ng/quickjs/releases/tag/v0.16.2

I'm trying to add quickjs-oxide to the tests, so it would be very helpful if you could provide prebuilt binaries.
https://github.com/ahaoboy/js-engine-benchmark/issues/44

Here is a set of test data I collected. It looks like there is still a lot of room for improvement compared to qjs.

cr --release --bin qjs /root/js-engine-benchmark/dist/run.js

Richards: 20.7
DeltaBlue: 29.2
Crypto: 36.6
RayTrace: 43.3
EarleyBoyer: 80.7
RegExp: 29.0
Splay: 172
NavierStokes: 56.6
----
Score: 46.5


qjs /root/js-engine-benchmark/dist/run.js
Richards: 766
DeltaBlue: 791
Crypto: 1088
RayTrace: 1325
EarleyBoyer: 1977
RegExp: 278
Splay: 2361
NavierStokes: 1140
----
Score: 1032
Dominant language
Rust
Stars
61
Forks
2
Avg merge
6d 10h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.