summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/main.c
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2016-05-16 18:14:07 +0000
committerNico Weber <nicolasweber@gmx.de>2016-05-16 18:14:07 +0000
commit379a1952b37247975d2df8d23498675c9c8cc730 (patch)
tree0c7f914499c302a7ad9a1fcf6ebeff0bbea87f7e /lldb/packages/Python/lldbsuite/test/python_api/value/main.c
parenta5bd2954e24be344f66fe1a019ee91cac14fced9 (diff)
downloadbcm5719-llvm-379a1952b37247975d2df8d23498675c9c8cc730.tar.gz
bcm5719-llvm-379a1952b37247975d2df8d23498675c9c8cc730.zip
[ms] Reintroduce feature guards in intrinsic headers in Microsoft mode
Visual Studio's C++ standard library headers include intrin.h, so the intrinsic headers get included a lot more often in Microsoft mode than elsewhere. The AVX512 intrinsics are a lot of code (0.7 MB, causing 30% compile time overhead for small programs including e.g. <string> and 6% compile time overhead for larger projects like e.g. v8). Since multiversioning can't be relied on in Microsoft mode (cl.exe doesn't support it), having faster compiles seems like the much better tradeoff until we have a better intrinsic story going forward (which we'll need for e.g. PR19898). Actually using intrinsics on Windows already requires the right /arch: settings, so this patch should have no big behavior change. See also thread "The intrinsics headers (especially avx512) are too big. What to do about it?" on cfe-dev. http://reviews.llvm.org/D20291 llvm-svn: 269675
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/main.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud