7519793938
This differs from the patch that landed in so far as the libm target is only defined if v8_use_libm_trig_functions is defined. Doing this ensures building the 'all' target only builds libm is appropriate. You can diff between patchset 1 and 2 to see the change. This is controlled by a gn arg, which defaults to true for clang builds. I'm limiting to clang builds as the macros for determining endian type are currently clang specific. My understanding is that chrome only uses clang. I can update the endian macros if necessary for other targets. Bug=v8:13477 Change-Id: I59cd450facc9fcb8987fe56e8cfc1c13522e1f6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4070924 Commit-Queue: Hannes Payer <hpayer@chromium.org> Auto-Submit: Scott Violet <sky@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/main@{#84620} |
||
|---|---|---|
| .. | ||
| colorama | ||
| glibc | ||
| google_benchmark | ||
| googletest | ||
| inspector_protocol | ||
| jsoncpp | ||
| test262-harness | ||
| v8/builtins | ||
| wasm-api | ||