-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove mprotect()/rwx
-related patch entry from bazel/v8.patch
#23258
Comments
Seems like we are aiming for 10.7: #23257 (review) |
@PiotrSikora I tried to upgrade v8, however, I stumbled upon: https://chromium-review.googlesource.com/c/v8/v8/+/3834031. Do you think we need to have this enabled by default too (hence reverting that commit) + adding a flag to enable Note: zlib is enabled by default in 10.7-lkgr: https://github.com/v8/v8/blob/6c8b357a84847a479cd329478522feefc1c3195a/BUILD.gn#L373-L376. |
@dio you can ignore it, snapshot compression was never enabled in the Bazel build anyway. Did you run into any issues because of that change? |
No. Without zlib we're good. Thanks! @PiotrSikora I asked since previously we patched zlib header path. |
Submitted proxy-wasm/proxy-wasm-cpp-host#310 to have proxy-wasm-cpp-host to use newer V8, 10.7.193.13 (with some updated |
Seems like proxy-wasm/proxy-wasm-cpp-host#310 is merged (the updated v8 version is v10.7.193.13). I can set up my own bucket at first to serve the required snapshot for submitting a PR (to upgrade the v8 version for Envoy), but then we need someone who has access to provide the snapshot on https://storage.googleapis.com/envoyproxy-wee8 (ref: envoy/bazel/repository_locations.bzl Line 1058 in e5ec3da
cc. @envoyproxy/wasm-dev |
@mpwarres should have access to generate and upload them. |
Ack, ran out of time to do this today, but will get to it tomorrow. |
The following files have been added to the https://storage.googleapis.com/envoyproxy-wee8 bucket: v8-10.7.193.13.tar.gz |
Thanks, @mpwarres! |
A patch is introduced by #23257 to fix
MemoryAllocator::PartialFreeMemory()
on v810.4.132.18
(envoy/bazel/repository_locations.bzl
Line 1053 in ad80029
That patch is copied from https://chromium-review.googlesource.com/c/v8/v8/+/3700352. That commit on v8 upstream is included in
10.5
(can be checked from10.5-lkgr
: https://chromium.googlesource.com/v8/v8.git/+/refs/heads/10.5-lkgr/src/heap/memory-allocator.cc#407) hence when we adopt 10.5 or higher, we should remove that patch (probably most of the patches will be removed/adapted anyway).The text was updated successfully, but these errors were encountered: