nodejs / nodejs/node

Compilation issues on i586

Open
#64,021 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

build experimental v8 engine
Dominant language
JavaScript
Stars
122k
Forks
37.3k
Avg merge
4d 2h
Merged PRs (30d)
283

Description

Looks like there's a build failure on linux 32-bit x86 only. (openSUSE Tumbleweed i586 arch)

[  845s] In file included from ../src/util.h:29,
[  845s]                  from ../src/crypto/crypto_clienthello-inl.h:28,
--
[ 2893s] ../deps/v8/src/strings/string-hasher.cc:29:12: error: ‘_mm_cvtsi128_si64’ was not declared in this scope; did you mean ‘_mm_cvtsi32_si64’?
[ 2893s]    29 |     return _mm_cvtsi128_si64(_mm_packus_epi16(x, x));
[ 2893s]       |            ^~~~~~~~~~~~~~~~~
[ 2893s]       |            _mm_cvtsi32_si64
[ 2893s] ../deps/v8/src/strings/string-hasher.cc: In static member function ‘static uint64_t v8::internal::ConvertTo8BitHashReader::Read32(const uint8_t*)’:
[ 2893s] ../deps/v8/src/strings/string-hasher.cc:50:12: error: ‘_mm_cvtsi128_si64’ was not declared in this scope; did you mean ‘_mm_cvtsi32_si64’?
[ 2893s]    50 |     return _mm_cvtsi128_si64(_mm_packus_epi16(x, x));
[ 2893s]       |            ^~~~~~~~~~~~~~~~~
[ 2893s]       |            _mm_cvtsi32_si64

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.

Research direction

Start with deps/v8/src/strings/string-hasher.cc and the reported _mm_cvtsi128_si64 errors, then reproduce the build on Linux 32-bit x86, such as openSUSE Tumbleweed i586. Determine the appropriate change for this architecture and verify that the Node.js build completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.