Skip to content

build: do not use bundled simdutf when built with --shared-simdutf - #65891

Open
aduh95 wants to merge 4 commits into
nodejs:mainfrom
aduh95:shared-simdutf
Open

build: do not use bundled simdutf when built with --shared-simdutf#65891
aduh95 wants to merge 4 commits into
nodejs:mainfrom
aduh95:shared-simdutf

Conversation

@aduh95

@aduh95 aduh95 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Now that v8/v8@a0607c5 has landed, we can mixing more than one simdutf instance. I'm also using this opportunity to clean up the $CONFIG_FLAGS generation is shell.nix, to not explicitly pass the lib and header paths to test our default values.

Original commit message:

    Rewrite simdutf include paths to allow getting it from system

    Change-Id: I2b7b4cb452c22ed72e0935662c3c7477954bc205
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8319848
    Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
    Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
    Reviewed-by: Omer Katz <omerkatz@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#109702}

Refs: v8/v8@a0607c5
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/actions
  • @nodejs/gyp
  • @nodejs/security-wg
  • @nodejs/v8-update

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to Node.js builds or CI infrastructure. meta Issues and PRs related to the general management of the project. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency. labels Sep 7, 2026
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor
Platform Number of requisites Proportion of new derivations
x86_64-linux 501 -> 502 => +1 1 / 502 = 0.1%
aarch64-linux 502 -> 503 => +1 1 / 503 = 0.1%
x86_64-darwin 441 -> 442 => +1 1 / 442 = 0.2%
aarch64-darwin 444 -> 445 => +1 1 / 445 = 0.2%
Total 1888 -> 1892 => +4 4 / 1892 = 0.2%
Changelog
@@ -1707,0 +1708,2 @@
+/nix/store/qcx56k9ydsfqb0rf7aqvwr5bn2garm6k-simdutf-9.0.0 (aarch64-darwin)
+/nix/store/kcxcfg1qwkbz5v4g2xqsr2vya9dfikvx-simdutf-9.0.0 (aarch64-linux)
@@ -1708,0 +1711 @@
+/nix/store/hk944pibnxikndqzisn9yij3ldxbi8fx-simdutf-9.0.0 (x86_64-darwin)
@@ -1710,0 +1714 @@
+/nix/store/jr66csw2kp4975f2ih9605z0srqnx4vc-simdutf-9.0.0 (x86_64-linux)

@aduh95 aduh95 added dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. labels Sep 7, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@codecov

codecov Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.17%. Comparing base (b4c83f5) to head (20a9a57).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #65891   +/-   ##
=======================================
  Coverage   90.16%   90.17%           
=======================================
  Files         771      771           
  Lines      265094   265097    +3     
  Branches    50367    50360    -7     
=======================================
+ Hits       239035   239062   +27     
+ Misses      17000    16971   -29     
- Partials     9059     9064    +5     

see 26 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@meixg meixg added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 8, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 8, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to Node.js builds or CI infrastructure. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. meta Issues and PRs related to the general management of the project. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants