Skip to content

build(v8): update rusty_v8 to 149.2.0#26464

Merged
cconger merged 5 commits into
mainfrom
cconger/update-rusty-v8-latest
Jun 6, 2026
Merged

build(v8): update rusty_v8 to 149.2.0#26464
cconger merged 5 commits into
mainfrom
cconger/update-rusty-v8-latest

Conversation

@cconger

@cconger cconger commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

+ "@v8//bazel/config:is_windows": ["/OPT:NOICF"],

P1 Badge Use GNU-compatible no-ICF flag for gnullvm

For Bazel builds targeting windows-gnullvm, @v8//bazel/config:is_windows is true, but the toolchain is GNU/clang-style rather than MSVC (.bazelrc's ci-windows-cross platform and this repo's V8 README both describe windows-gnullvm/x86_64-w64-windows-gnu). I checked clang's MinGW driver behavior with clang --target=x86_64-w64-windows-gnu -### ... /OPT:NOICF, and it treats /OPT:NOICF as an input path, so any Windows-GNU V8 build that reaches mksnapshot will fail before linking. Use the GNU/lld spelling for this branch (or select MSVC separately) instead of the MSVC /OPT:NOICF flag.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@cconger cconger force-pushed the cconger/update-rusty-v8-latest branch from c1f0297 to 336d10b Compare June 5, 2026 04:20
@cconger cconger merged commit b89ce9a into main Jun 6, 2026
46 checks passed
@cconger cconger deleted the cconger/update-rusty-v8-latest branch June 6, 2026 21:27
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants