-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
v8: update v8 patch to avoid breaking building with clang #52303
Conversation
Review requested:
|
@zcbenz Unfortunately this breaks compilation with MSVC. |
c491545
to
50735b2
Compare
50735b2
to
c3bc66a
Compare
It turns out the |
Can you also try upstream those changes ? |
This PR means to fix the breakages introduced by b9d806a, according to its commit message it is not going to be upstreamed, so neither will this change. |
You are correct, this will not be upstreamed. @zcbenz, as a part of work on #52293 I'm porting my patch there (cannot apply cleanly because the files it modifies were changed in the meantime). Once it's ready (eg. working on all platforms), I'll let you know and we can apply your changes before landing it in the V8 update branch, so it's all there together. |
@zcbenz just to let you know that neither V8, nor its patches I made starting from v12.3 have |
Thanks for letting me know! I'll give it a try. |
When building with C++20 using a very new clang (which is used by the GN build), compilation would fail caused because of the change in b9d806a.
The detailed errors can be found in:
https://github.com/photoionization/node_with_gn/actions/runs/8501717771/job/23284924676
My understanding of the error is that, after changing
if constexpr
toif
, some code that were not supposed to be compiled are now compiled, and it is causing problems for certain compiler settings.