|
|
Created:
4 years, 7 months ago by saiarcot895 Modified:
4 years, 7 months ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionAdd SSE2/MMX build flags when building on an x86 host. This is necessary
because some files use SSE2 extensions, which may not be available on
all x86 CPUs.
BUG=607938
R=dpranke@chromium.org
Committed: https://crrev.com/bfb9e9ef5c13843e22a74a7bced0d48b6f42c112
Cr-Commit-Position: refs/heads/master@{#392206}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Moved to compiler_cpu_abi config, and fixed for NaCl build #Messages
Total messages: 20 (6 generated)
dpranke@chromium.org changed reviewers: + thakis@chromium.org
I'm not close enough to how these compiler flags work on different host cpus, so I'm not sure what's the default and what needs to be explicitly set these days. So, I'm punting this to thakis, who hopefully knows this stuff; if not, he can re-punt. However, ... 1) Doesn't chromium require SSE2 nowadays? 2) If we do need to change things, this change should be part of the 'compiler_cpu_abi' config, not the base config.
lgtm; from what I understand this ports https://codereview.chromium.org/187423002 to gn https://codereview.chromium.org/1952043003/diff/1/build/config/compiler/BUILD.gn File build/config/compiler/BUILD.gn (right): https://codereview.chromium.org/1952043003/diff/1/build/config/compiler/BUILD... build/config/compiler/BUILD.gn:226: "-mmmx", doesn't msse2 imply mmx?
https://codereview.chromium.org/1952043003/diff/1/build/config/compiler/BUILD.gn File build/config/compiler/BUILD.gn (right): https://codereview.chromium.org/1952043003/diff/1/build/config/compiler/BUILD... build/config/compiler/BUILD.gn:226: "-mmmx", On 2016/05/05 at 17:33:23, Nico wrote: > doesn't msse2 imply mmx? It might (based on the options for the -march flag and the extensions it sets), but it's not explicitly stated in the GCC documentation.
The CQ bit was checked by saiarcot895@gmail.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1952043003/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1952043003/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromeos_x86-generic_chromium_compile_only_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)
PTAL. The CFLAGS addition has been moved to the compiler_cpu_abi config section, and the code has been fixed to not add the flags when using the NaCl toolchain, which should fix the trybot failure.
lgtm
The CQ bit was checked by dpranke@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from thakis@chromium.org Link to the patchset: https://codereview.chromium.org/1952043003/#ps20001 (title: "Moved to compiler_cpu_abi config, and fixed for NaCl build")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1952043003/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1952043003/20001
Hm, in the new location clang-cl won't see these flags.
On 2016/05/06 22:38:54, Nico wrote: > Hm, in the new location clang-cl won't see these flags. Yup, as you no doubt know, there's a bunch of duplication between posix-y configs and win-clang configs. I don't think fixing that is in the scope of this particular tiny change.
This is adding flags missing in the gn build; might as well do it right (if (is_clang or not win) and ia32) On May 6, 2016 6:45 PM, <dpranke@chromium.org> wrote: > On 2016/05/06 22:38:54, Nico wrote: > > Hm, in the new location clang-cl won't see these flags. > > Yup, as you no doubt know, there's a bunch of duplication between posix-y > configs and win-clang configs. I don't think fixing that is in the scope > of this > particular tiny change. > > https://codereview.chromium.org/1952043003/ > -- You received this message because you are subscribed to the Google Groups "Chromium-reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Add SSE2/MMX build flags when building on an x86 host. This is necessary because some files use SSE2 extensions, which may not be available on all x86 CPUs. BUG=607938 R=dpranke@chromium.org ========== to ========== Add SSE2/MMX build flags when building on an x86 host. This is necessary because some files use SSE2 extensions, which may not be available on all x86 CPUs. BUG=607938 R=dpranke@chromium.org Committed: https://crrev.com/bfb9e9ef5c13843e22a74a7bced0d48b6f42c112 Cr-Commit-Position: refs/heads/master@{#392206} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/bfb9e9ef5c13843e22a74a7bced0d48b6f42c112 Cr-Commit-Position: refs/heads/master@{#392206} |