summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Revert r283057 and r283058Sanjoy Das2016-10-023-91/+124
| | | | | | | | | | | They've broken the sanitizer-bootstrap bots. Reverting while I investigate. Original commit messages: r283057: "[ConstantRange] Make getEquivalentICmp smarter" r283058: "[SCEV] Rely on ConstantRange instead of custom logic; NFCI" llvm-svn: 283062
* [PowerPC] Enable soft-float for PPC64, and +soft-float -> -hard-floatHal Finkel2016-10-024-26/+202
| | | | | | | | | | Enable soft-float support on PPC64, as the backend now supports it. Also, the backend now uses -hard-float instead of +soft-float, so set the target features accordingly. Fixes PR26970. llvm-svn: 283061
* [PowerPC] Refactor soft-float support, and enable PPC64 soft floatHal Finkel2016-10-026-26/+45
| | | | | | | | | | | | | | | | | | | | | | | This change enables soft-float for PowerPC64, and also makes soft-float disable all vector instruction sets for both 32-bit and 64-bit modes. This latter part is necessary because the PPC backend canonicalizes many Altivec vector types to floating-point types, and so soft-float breaks scalarization support for many operations. Both for embedded targets and for operating-system kernels desiring soft-float support, it seems reasonable that disabling hardware floating-point also disables vector instructions (embedded targets without hardware floating point support are unlikely to have Altivec, etc. and operating system kernels desiring not to use floating-point registers to lower syscall cost are unlikely to want to use vector registers either). If someone needs this to work, we'll need to change the fact that we promote many Altivec operations to act on v4f32. To make it possible to disable Altivec when soft-float is enabled, hardware floating-point support needs to be expressed as a positive feature, like the others, and not a negative feature, because target features cannot have dependencies on the disabling of some other feature. So +soft-float has now become -hard-float. Fixes PR26970. llvm-svn: 283060
* Remove duplicated code; NFCSanjoy Das2016-10-026-73/+7
| | | | | | | ICmpInst::makeConstantRange does exactly the same thing as ConstantRange::makeExactICmpRegion. llvm-svn: 283059
* [SCEV] Rely on ConstantRange instead of custom logic; NFCISanjoy Das2016-10-021-124/+52
| | | | llvm-svn: 283058
* [ConstantRange] Make getEquivalentICmp smarterSanjoy Das2016-10-022-0/+39
| | | | | | | This change teaches getEquivalentICmp to be smarter about generating ICMP_NE and ICMP_EQ predicates. llvm-svn: 283057
* [SCEV] Remove commented out code; NFCSanjoy Das2016-10-021-3/+1
| | | | llvm-svn: 283056
* COFF: Fix short import lib import name type bitshiftMartell Malone2016-10-013-1/+5
| | | | | | | | | | | | | | As per the PE COFF spec (section 8.3, Import Name Type) Offset: 18 Size 2 bits Name: Type Offset: 20 Size 3 bits Name: Name Type Offset: 20 added based on 18+2 Partially commited as rL279069 Differential Revision: https://reviews.llvm.org/D23540 llvm-svn: 283055
* [AVX-512] Check rounding mode for builtins that take one. Rounding mode ↵Craig Topper2016-10-011-0/+93
| | | | | | should be either _MM_FROUND_CUR_DIRECTION or a 2-bit rounding mode ORed with _MM_FROUND_NO_EXC. llvm-svn: 283054
* [AVX-512] Add _MM_FROUND_NO_EXC to test cases that pass a rounding mode ↵Craig Topper2016-10-012-120/+120
| | | | | | intrinsics. This is preparation for a follow up commit that will check validity of rounding mode argument. llvm-svn: 283053
* Remove some additional unnecessary std:: in cmathHal Finkel2016-10-011-9/+9
| | | | | | | Unlike in math.h, as Eric pointed out in the review of D18639, we don't need the std:: in cmath. llvm-svn: 283052
* Use __builtin_isnan/isinf/isfinite in complexHal Finkel2016-10-012-80/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The libc-provided isnan/isinf/isfinite macro implementations are specifically designed to function correctly, even in the presence of -ffast-math (or, more specifically, -ffinite-math-only). As such, on most implementation, these either always turn into external function calls (e.g. glibc) or are specifically function calls when FINITE_MATH_ONLY is defined (e.g. Darwin). Our implementation of complex arithmetic makes heavy use of isnan/isinf/isfinite to deal with corner cases involving non-finite quantities. This was problematic in two respects: 1. On systems where these are always function calls (e.g. Linux/glibc), there was a performance penalty 2. When compiling with -ffast-math, there was a significant performance penalty (in fact, on Darwin and systems with similar implementations, the code may in fact be slower than not using -ffast-math, because the inline definitions provided by libc become unavailable to prevent the checks from being optimized out). Eliding these inf/nan checks in -ffast-math mode is consistent with what happens with libstdc++, and in my experience, what users expect. This is critical to getting high-performance code when using complex<T>. This change replaces uses of those functions on basic floating-point types with calls to __builtin_isnan/isinf/isfinite, which Clang will always expand inline. When using -ffast-math (or -ffinite-math-only), the optimizer will remove the checks as expected. Differential Revision: https://reviews.llvm.org/D18639 llvm-svn: 283051
* [X86][SSE] Cleaned up shuffle decode assertion messagesSimon Pilgrim2016-10-011-7/+11
| | | | llvm-svn: 283050
* isl: update to isl-0.17.1-233-gc911e6aTobias Grosser2016-10-0121-517/+1168
| | | | llvm-svn: 283049
* [SLPVectorizer][X86] Added fptosi/fptoui testsSimon Pilgrim2016-10-012-0/+1146
| | | | llvm-svn: 283048
* [CostModel][X86] Added tests for current fptosi/fptoui costsSimon Pilgrim2016-10-012-0/+501
| | | | llvm-svn: 283047
* [SLPVectorizer][X86] Added fcopysign testsSimon Pilgrim2016-10-011-0/+404
| | | | llvm-svn: 283046
* [SLPVectorizer][X86] Added fabs testsSimon Pilgrim2016-10-011-0/+274
| | | | llvm-svn: 283045
* [CostModel][X86] Added fcopysign costsSimon Pilgrim2016-10-011-0/+65
| | | | llvm-svn: 283044
* Use StringRef for MemoryBuffer identifier API (NFC)Mehdi Amini2016-10-0119-45/+42
| | | | llvm-svn: 283043
* [CostModel][X86] Added fabs costsSimon Pilgrim2016-10-011-0/+65
| | | | llvm-svn: 283042
* Fix signed/unsigned warningSimon Pilgrim2016-10-011-2/+2
| | | | llvm-svn: 283041
* [X86][SSE] Add support for combining target shuffles to binary BLENDSimon Pilgrim2016-10-013-12/+34
| | | | | | We already had support for 1-input BLEND with zero - this adds support for 2-input BLEND as well. llvm-svn: 283040
* Use StringRef in Registry API (NFC)Mehdi Amini2016-10-013-10/+9
| | | | llvm-svn: 283039
* [X86][SSE] Always combine target shuffles to MOVSD/MOVSSSimon Pilgrim2016-10-019-41/+92
| | | | | | | | Now we can commute to BLENDPD/BLENDPS on SSE41+ targets if necessary, so simplify the combine matching where we can. This required me to add a couple of scalar math movsd/moss fold patterns that hadn't been needed in the past. llvm-svn: 283038
* [X86][SSE] Enable commutation from MOVSD/MOVSS to BLENDPD/BLENDPS on SSE41+ ↵Simon Pilgrim2016-10-017-50/+160
| | | | | | | | | | | | targets Instead of selecting between MOVSD/MOVSS and BLENDPD/BLENDPS at shuffle lowering by subtarget this will help us select the instruction based on actual commutation requirements. We could possibly add BLENDPD/BLENDPS -> MOVSD/MOVSS commutation and MOVSD/MOVSS memory folding using a similar approach if it proves useful I avoided adding AVX512 handling as I'm not sure when we should be making use of VBLENDPD/VBLENDPS on EVEX targets llvm-svn: 283037
* Revert r283029 - [cmake] Make LIT_COMMAND configurable and improve fallback ↵Michal Gorny2016-10-011-4/+3
| | | | | | | | | | | | | | support Revert the change in r283029 (and the fixup in r283033) due to buildbot breakage. The fixup is ineffective for the bots that do not force clean build since the wrong value is already cached in CMakeCache.txt. Reverting it should result in the cache variable being removed and therefore it should be possible to re-introduce it after all buildbots build this revision. llvm-svn: 283036
* [X86][SSE] Regenerate vselect tests and improve AVX1/AVX2 coverageSimon Pilgrim2016-10-013-193/+507
| | | | llvm-svn: 283035
* Revert "[MC] Prevent out of order HashDirective lexing in AsmLexer."Nirav Dave2016-10-013-26/+27
| | | | | | This reverts commit r282992 which appears to be causing an LTO test failure. llvm-svn: 283034
* [cmake] Fix incorrect default for LIT_COMMAND, from r283029Michal Gorny2016-10-011-1/+1
| | | | llvm-svn: 283033
* Remove all instances of _LIBCPP_HAS_NO_RVALUE_REFERENCES from test/std/utilitiesEric Fiselier2016-10-0145-209/+118
| | | | llvm-svn: 283032
* [lldb-mi] Fix prompt which can get inserted in the middle of program output ↵Dawn Perchik2016-10-011-1/+3
| | | | | | | | | | | | | | in lldb-mi Summary: The code added in svn r264332 causes "(lldb) " to be printed in the middle of program console output. This fix restores the behavior for non-Windows platforms to before the patch. Reviewers: ted, zturner, clayborg Subscribers: amccarth, lldb-commits Differential Revision: http://reviews.llvm.org/D25137 llvm-svn: 283031
* Replace test_throw.h header with a single test macroEric Fiselier2016-10-018-39/+17
| | | | llvm-svn: 283030
* [cmake] Make LIT_COMMAND configurable and improve fallback supportMichal Gorny2016-10-011-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make LIT_COMMAND configurable, use source tree only when actually available and extend the default search to other common executable names 'lit.py' and 'lit', in order to increase uniformity between all LLVM projects and support using installed lit. Changing the conditional used to determine whether in-tree or external lit is being used covers the case when LLVM_MAIN_SRC_DIR is defined but does not exist (anymore). In this case, the functions falls back to looking for installed lit rather than attempting to use a non-existing path. The same conditional is used in clang already. Making LIT_COMMAND a cache variable in case the source tree variant is used serves two purposes. Firstly, it increases uniformity between the two branches since find_program() implicitly makes LIT_COMMAND a cache variable. Secondly, it allows overriding the lit executable used to run the tests when the LLVM source tree is provided. Gentoo is planning to use this to use installed (and byte-compiled) lit instead of re-compiling it in every LLVM project. Extending default search is meant to increase uniformity between different LLVM projects. The 'lit.py' name is already used by a few of them, and 'lit' is the name used by utils/lit/setup.py when installing. Differential Revision: https://reviews.llvm.org/D25076 llvm-svn: 283029
* [OCaml] Install .mli (interface) filesMichal Gorny2016-10-011-1/+2
| | | | | | | | | | | | | Install the OCaml interface .mli files. Those files were most likely omitted because they are input files for the compiled .cmi files. However, installing them is reasonable since -- unlike .cmi files -- they are human-readable. The issue was originally spotted by @jpdeplaix. Differential Revision: https://reviews.llvm.org/D25128 llvm-svn: 283028
* Split a comment into generic description and note about the specificJoerg Sonnenberger2016-10-011-3/+2
| | | | | | cmake use. llvm-svn: 283027
* Retire LLVM_BINDIR and friends. They haven't been provided with actualJoerg Sonnenberger2016-10-012-42/+0
| | | | | | values since the switch to cmake. llvm-svn: 283026
* [libFuzzer] add fuzzer test for libxml2, finds ↵Kostya Serebryany2016-10-013-0/+38
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=751631 llvm-svn: 283024
* GC HAVE_STRTOQJoerg Sonnenberger2016-10-012-4/+0
| | | | llvm-svn: 283023
* Retire bugpoint's -R. hack.Joerg Sonnenberger2016-10-013-13/+2
| | | | | | | | | It got disconnected during the cmake conversion. For Miscompilation.cpp, it was purely advisory for the user and the ToolRunner.cpp version was trying to compensate for libs and bins in the same directory, which hasn't been the case for a very long time. llvm-svn: 283022
* [libFuzzer] fix a recent bugs (buffer overflow)Kostya Serebryany2016-10-011-1/+1
| | | | llvm-svn: 283021
* [X86] Cleanup patterns for using VMOVDDUP for broadcasts.Craig Topper2016-10-013-13/+18
| | | | | | | | -Remove OptForSize. Not all of the backend follows the same rules for creating broadcasts and there is no conflicting pattern. -Don't stop selecting VEX VMOVDDUP when AVX512 is supported. We need VLX for EVEX VMOVDDUP. -Only use VMOVDDUP for v2i64 broadcasts if AVX2 is not supported. llvm-svn: 283020
* Revert "Use StringRef instead of raw pointer in TargetRegistry API (NFC)"Mehdi Amini2016-10-014-15/+15
| | | | | | This reverts commit r283017. Creates an infinite loop somehow. llvm-svn: 283019
* Use StringRef instead of raw pointers in MCAsmInfo/MCInstrInfo APIs (NFC)Mehdi Amini2016-10-0116-55/+55
| | | | llvm-svn: 283018
* Use StringRef instead of raw pointer in TargetRegistry API (NFC)Mehdi Amini2016-10-014-15/+15
| | | | llvm-svn: 283017
* Use StringRef instead of raw pointer in ExecutionEngineMehdi Amini2016-10-015-14/+14
| | | | llvm-svn: 283016
* [AVX-512] Add EVEX versions of VPBROADCASTW patterns with truncated i32 loads.Craig Topper2016-10-012-1/+18
| | | | llvm-svn: 283015
* [AVX-512] Add VLX command lines to 128 and 256-bit shufffle tests.Craig Topper2016-10-016-1405/+2920
| | | | llvm-svn: 283014
* Use StringRef in Datalayout API (NFC)Mehdi Amini2016-10-014-6/+6
| | | | llvm-svn: 283013
* DIFlags: use StringRef instead of raw pointer (NFC)Mehdi Amini2016-10-013-4/+4
| | | | llvm-svn: 283012
OpenPOWER on IntegriCloud