Extend shared simdutf flag to v8

Open Beginner friendly
#60,984 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
cpp, node.js, python
Domain
build-system

Research direction

Start with configure.py's existing --shared-simdutf* flags and tools/v8_gypfiles/v8.gyp. Trace how the shared simdutf option is represented in the V8 build configuration, then update the V8 target so it can use the shared copy. Done means the V8 build path honors the flag without embedding another simdutf copy; verify by configuring and building with the shared option.

Written by the indexing model from the issue text.

Description

feature request
What is the problem this feature will solve?

configure.py has --shared-simdutf* flags, but now v8 embeds another copy of simdutf as well.

What is the feature you are proposing to solve the problem?

It would be awesome if tools/v8_gypfiles/v8.gyp was updated to allow linking v8 to the shared simdutf copy.

What alternatives have you considered?

No response

Dominant language
JavaScript
Stars
122k
Forks
37.4k
Avg merge
4d 3h
Merged PRs (30d)
273

Contributor guide

Open the contributing guide

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.

More from nodejs/node

All issues in nodejs/node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.