You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(not sure if this issue should go here or in nodejs/node. I can move it there if needed)
One of the blocking issues to update V8 to 6.7 is related to a behavior change on clang after 3.9. There's an upstream CL (https://chromium-review.googlesource.com/c/v8/v8/+/1050666) to fix the issue for now, but I'm sure it will happen again. Upstream patches are fine as a short-term solution, but it won't take long before we start to hit bigger issues with clang version discrepancy. Besides, we're supporting a compiler version from 2014, while our oldest active release line (v6.x) was released on 2016.
I know we can't do such a huge requirement upgrade on our current release lines, but I believe we should start to plan on upgrading our minimum clang requirement to at least 3.9 (ideally 4.0) in a future semver-major (12, 13 maybe?).
Any thoughts on this?
The text was updated successfully, but these errors were encountered:
(not sure if this issue should go here or in nodejs/node. I can move it there if needed)
One of the blocking issues to update V8 to 6.7 is related to a behavior change on clang after 3.9. There's an upstream CL (https://chromium-review.googlesource.com/c/v8/v8/+/1050666) to fix the issue for now, but I'm sure it will happen again. Upstream patches are fine as a short-term solution, but it won't take long before we start to hit bigger issues with clang version discrepancy. Besides, we're supporting a compiler version from 2014, while our oldest active release line (v6.x) was released on 2016.
I know we can't do such a huge requirement upgrade on our current release lines, but I believe we should start to plan on upgrading our minimum clang requirement to at least 3.9 (ideally 4.0) in a future semver-major (12, 13 maybe?).
Any thoughts on this?
The text was updated successfully, but these errors were encountered: