summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Create a PT_LOAD program header for the start of the file.Rafael Espindola2015-09-1012-56/+123
| | | | | | | | With this a trivial dynamic program works with the musl dynamic linker: LD_LIBRARY_PATH=. ~/musl/lib/libc.so ./t llvm-svn: 247290
* Allow general loops with one latchJohannes Doerfert2015-09-1019-228/+286
| | | | | | | | | | | | | | | | | | | As we do not rely on ScalarEvolution any more we do not need to get the backedge taken count. Additionally, our domain generation handles everything that is affine and has one latch and our ScopDetection will over-approximate everything else. This change will therefor allow loops with: - one latch - exiting conditions that are affine Additionally, it will not check for structured control flow anymore. Hence, loops and conditionals are not necessarily single entry single exit regions any more. Differential Version: http://reviews.llvm.org/D12758 llvm-svn: 247289
* Merge TempScopInfo into ScopInfoMichael Kruse2015-09-1020-152/+85
| | | | | | | | | | | | | The TempScopInfo (-polly-analyze-ir) pass is removed and its work taken over by ScopInfo (-polly-scops). Several tests depend on -polly-analyze-ir and use -polly-scops instead which for the moment prints the output of both passes. This again is not expected by some other tests, especially those with negative searches, which have been adapted. Differential Version: http://reviews.llvm.org/D12694 llvm-svn: 247288
* fix typo; NFCSanjay Patel2015-09-101-1/+1
| | | | llvm-svn: 247287
* Properly close documentation /code blocks with /endcode.Aaron Ballman2015-09-101-9/+10
| | | | llvm-svn: 247286
* Clean-up unit testsMichael Kruse2015-09-1031-38/+6
| | | | | | Remove redundant flags and duplicate invocations of the same test. llvm-svn: 247285
* Build Plugin/JITLoader/GDB on all platforms.Bruce Mitchener2015-09-102-7/+1
| | | | | | | | | | | | | | | Summary: We currently link to this on all platforms, so don't need to re-include it into the LLDB_USED_LIBS. Also don't need to special case building it for every supported platform. Reviewers: clayborg, labath Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D12756 llvm-svn: 247284
* Fix PR 24724 - The implicit register verifier shouldn't assume certain operandAlex Lorenz2015-09-105-41/+65
| | | | | | | | | | order. The implicit register verifier in the MIR parser should only check if the instruction's default implicit operands are present in the instruction. It should not check the order in which they occur. llvm-svn: 247283
* [clang-tidy] add_new_check.py improvements: add doc file, refer it from .hAlexander Kornienko2015-09-101-13/+59
| | | | | | + some console logging and minor cleanups. llvm-svn: 247282
* Cleaning up LLVM IR mode for Emacs.Rafael Espindola2015-09-101-78/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've made a range of improvements to the Emacs mode for LLVM IR. Most importantly, it changes llvm-mode to inherit from prog-mode. This means llvm-mode will be treated as a normal programming mode in Emacs, so many Emacs features will just work. prog-mode is new to Emacs 24, so I've added an alias to ensure compatibility with Emacs 23 too. I've changed the mode definition to use define-derived-mode. This saves us needing to set up local variables ourselves, and saves us needing to define llvm-mode-map, llvm-mode-abbrev-table, llvm-mode-map. I've removed the keybindings to tab-to-tab-stop, center-line and center-paragraph. This shouldn't be llvm-mode's responsibility, and the code didn't actually work anyway (since `(not llvm-mode-map)` always evaluated to `t`, the keybindings were never executed). I've simplified the syntax-table definition, it's equivalent (e.g. `"` is treated as string delimiter by default in Emacs). I've added `.` as a symbol constituent, so functions like `llvm.memset.p0i8.i32` are recognised as a single symbol. I've also changed `%` to be a symbol constituent, so users can move between words or symbols at their choice, rather than conflating the two. I've fixed regexp for types, which incorrect used `symbol` instead of `symbols` as an argument to `regexp-opt`. This was causing incorrect highlighting on lines like `call void @foovoid`. I've removed string and comment highlighting from `llvm-font-lock-keywords`. This is already handled by the syntax-table. Finally, I've removed the reference to jasmin. That project is long abandoned and the link 404s. For reference, I've found an old copy of the project here: https://github.com/stevej/emacs/blob/master/vendor/jasmin/jasmin.el Patch by Wilfred Hughes! llvm-svn: 247281
* [NFC] Remove obsolete argumentsJohannes Doerfert2015-09-102-23/+17
| | | | | | | Remove some arguments that survived the recent changes but are not used any more. llvm-svn: 247280
* Replace ScalarEvolution based domain generationJohannes Doerfert2015-09-1022-195/+630
| | | | | | | | | | | | | | | | | | | | | | This patch replaces the last legacy part of the domain generation, namely the ScalarEvolution part that was used to obtain loop bounds. We now iterate over the loops in the region and propagate the back edge condition to the header blocks. Afterwards we propagate the new information once through the whole region. In this process we simply ignore unbounded parts of the domain and thereby assume the absence of infinite loops. + This patch already identified a couple of broken unit tests we had for years. + We allow more loops already and the step to multiple exit and multiple back edges is minimal. + It allows to model the overflow checks properly as we actually visit every block in the SCoP and know where which condition is evaluated. - It is currently not compatible with modulo constraints in the domain. Differential Revision: http://reviews.llvm.org/D12499 llvm-svn: 247279
* Disable support for modulo expressionsJohannes Doerfert2015-09-107-11/+47
| | | | | | | | | The support for modulo expressions is not comlete and makes the new domain generation harder. As the currently broken domain generation needs to be replaced, we will first swap in the new, fixed domain generation and make it compatible with the modulo expressions later. llvm-svn: 247278
* AVX-512: Changed nidx parameter in extractf64/32 intrinsic from i8 to i32 ↵Igor Breger2015-09-101-2/+2
| | | | | | | | according to the Intel Spec Differential Revision: http://reviews.llvm.org/D12752 llvm-svn: 247277
* AVX512: Implemented encoding and intrinsics forIgor Breger2015-09-1012-89/+1145
| | | | | | | | | vextracti64x4 ,vextracti64x2, vextracti32x8, vextracti32x4, vextractf64x4, vextractf64x2, vextractf32x8, vextractf32x4 Added tests for intrinsics and encoding. Differential Revision: http://reviews.llvm.org/D11802 llvm-svn: 247276
* Silencing C4141 warnings that were introduced en masse because __forceinline ↵Aaron Ballman2015-09-101-0/+1
| | | | | | cannot be combined with inline in MSVC without triggering this diagnostic. This is safe to disable because clang will catch instances of the issue with -Wduplicate-decl-specifier, so we are not losing diagnostic coverage. llvm-svn: 247275
* Merge TempScopInfo.{cpp|h} into ScopInfo.{cpp|h}Michael Kruse2015-09-108-741/+662
| | | | | | | | | | | | | | | | | | This prepares for a series of patches that merges TempScopInfo into ScopInfo to reduce Polly's code complexity. Only ScopInfo.{cpp|h} will be left thereafter. Moving the code of TempScopInfo in one commit makes the mains diffs simpler to understand. In detail, merging the following classes is planned: TempScopInfo into ScopInfo TempScop into Scop IRAccess into MemoryAccess Only moving code, no functional changes intended. Differential Version: http://reviews.llvm.org/D12693 llvm-svn: 247274
* [OPENMP] Generate threadprivates as TLS variables by default.Alexey Bataev2015-09-102-4/+11
| | | | | | If target supports TLS all threadprivates are generated as TLS. If target does not support TLS, use runtime calls for proper codegen of threadprivate variables. llvm-svn: 247273
* [FileCheck] Use range-based for loops. NFC.Benjamin Kramer2015-09-101-26/+14
| | | | llvm-svn: 247272
* There is a trunc(lshr (zext A), Cst) optimization in InstCombineCasts thatJakub Kuderski2015-09-102-0/+68
| | | | | | | | | | | removes cast by performing the lshr on smaller types. However, currently there is no trunc(lshr (sext A), Cst) variant. This patch add such optimization by transforming trunc(lshr (sext A), Cst) to ashr A, Cst. Differential Revision: http://reviews.llvm.org/D12520 llvm-svn: 247271
* [OPENMP] Fix test incompatibility with Windows.Alexey Bataev2015-09-101-2/+2
| | | | llvm-svn: 247270
* [ADT] Rewrite the StringRef::find implementation to be simpler, clearer,Chandler Carruth2015-09-101-16/+23
| | | | | | | | | | | | | | | | and tremendously less reliant on the optimizer to fix things. The code is always necessarily looking for the entire length of the string when doing the equality tests in this find implementation, but it previously was needlessly re-checking the size each time among other annoyances. By writing this so simply an ddirectly in terms of memcmp, it also is about 8x faster in a debug build, which in turn makes FileCheck about 2x faster in 'ninja check-llvm'. This saves about 8% of the time for FileCheck-heavy parts of the test suite like the x86 backend tests. llvm-svn: 247269
* [OPENMP] Fix test incompatibility with Windows codegen.Alexey Bataev2015-09-101-1/+1
| | | | llvm-svn: 247268
* Fix crash in lldb-server caused by an API change in LLVMTamas Berghammer2015-09-101-1/+1
| | | | llvm-svn: 247267
* [clang-tidy] Renamed tests files to be closer to the check names.Alexander Kornienko2015-09-103-0/+0
| | | | llvm-svn: 247266
* [DAGCombine] Truncate BUILD_VECTOR operators if necessary when constant ↵Silviu Baranga2015-09-102-11/+37
| | | | | | | | | | | | | | | | | | | | | folding vectors Summary: The BUILD_VECTOR node will truncate its operators to match the type. We need to take this into account when constant folding - we need to perform a truncation before constant folding the elements. This is because the upper bits can change the result, depending on the operation type (for example this is the case for min/max). This change also adds a regression test. Reviewers: jmolloy Subscribers: jmolloy, llvm-commits Differential Revision: http://reviews.llvm.org/D12697 llvm-svn: 247265
* Enable GlobalsAA by defaultJames Molloy2015-09-101-1/+1
| | | | | | This can give significant improvements to alias analysis in some situations, and improves its testing coverage in all situations. llvm-svn: 247264
* Add GlobalsAA as preserved to a bunch of transformsJames Molloy2015-09-1014-0/+28
| | | | | | GlobalsAA must by definition be preserved in function passes, but the passmanager doesn't know that. Make each pass explicitly preserve GlobalsAA. llvm-svn: 247263
* New RenderScript command to break on all kernelsEwan Crawford2015-09-102-10/+169
| | | | | | | | | | | | | | | | Patch adds a command to RenderScript plugin allowing users to automatically set breakpoints on every RS kernel. Command syntax is 'language renderscript kernel breakpoint all <enable/disable>.' Enable sets breakpoints on all currently loaded kernels, and any kernels which will be loaded in future. Disable results in breakpoints no longer being set on loaded kernels, but doesn't affect existing breakpoints. Current command 'language renderscript kernel breakpoint' is changed to 'language renderscript kernel breakpoint set' Reviewed by: clayborg, jingham Subscribers: lldb-commits, ADodds, domipheus Differential Revision: http://reviews.llvm.org/D12728 llvm-svn: 247262
* [clang-tidy] Add inconsistent declaration parameter name checkAlexander Kornienko2015-09-107-0/+606
| | | | | | | | | | | | | | | | | | | | This is first of series of patches, porting code from my project colobot-lint, as I mentioned recently in cfe-dev mailing list. This patch adds a new check in readability module: readability-inconsistent-declaration-parameter-name. I also added appropriate testcases and documentation. I chose readability module, as it seems it is the best place for it. I think I followed the rules of LLVM coding guideline, but I may have missed something, as I usually use other code formatting style. http://reviews.llvm.org/D12462 Patch by Piotr Dziwinski! llvm-svn: 247261
* [OPENMP] Propagate alignment from original variables to the private copies.Alexey Bataev2015-09-106-80/+100
| | | | | | Currently private copies of captured variables have default alignment. Patch makes private variables to have same alignment as original variables. llvm-svn: 247260
* [ADT] Force inline several super boring and unusually hot methods onChandler Carruth2015-09-101-0/+7
| | | | | | | | | | | | | | SmallVector to further help debug builds not waste their time calling one line functions. To give you an idea of why this is worthwhile, this change alone gets another >10% reduction in the runtime of TripleTest.Normalization! It's now under 9 seconds for me. Sadly, this is the end of the easy wins for that test. Anything further will require some different architecture of the test itself. Still, I'm pretty happy. 'check-llvm' now is under 35s for me. llvm-svn: 247259
* Add a deprecation notice to the clang-modernize documentation.Alexander Kornienko2015-09-101-28/+9
| | | | | | | | | | | | | | Summary: Add a deprecation notice to the clang-modernize documentation. Remove the reference to the external JIRA tracker. Reviewers: revane, klimek Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D12732 llvm-svn: 247258
* [ADT] Micro-optimize and force inlining for string switches.Chandler Carruth2015-09-101-5/+45
| | | | | | | | | | | | | | These are now quite heavily used in unit tests and the host tools, making it worth having them be reasonably fast even in an unoptimized build. This change reduces the total runtime of TripleTest.Normalization by yet another 10% to 15%. It is now under 10 seconds on my machine, and the total check-llvm time has dropped from 38s to around 36s. I experimented with a number of different options, and the code pattern here consistently seemed to lower the cleanest, likely due to the significantly simple CFG and far fewer redundant tests of 'Result'. llvm-svn: 247257
* Fix an AttributeError in dotest.py if --executable points to a wrong placeIlia K2015-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This patch fixes the following case: ``` $ ./dotest.py --executable=~/p/llvm/build_ninja/bin/lldb tools/lldb-mi/ '~/p/llvm/build_ninja/bin/lldb' is not a path to a valid executable Traceback (most recent call last): File "./dotest.py", line 1306, in <module> setupSysPath() File "./dotest.py", line 1004, in setupSysPath if not lldbtest_config.lldbExec: AttributeError: 'module' object has no attribute 'lldbExec' ``` And with this fix: ``` $ ./dotest.py --executable=~/p/llvm/build_ninja/bin/lldb tools/lldb-mi/ '~/p/llvm/build_ninja/bin/lldb' is not a path to a valid executable The 'lldb' executable cannot be located. Some of the tests may not be run as a result. ``` llvm-svn: 247256
* [OPENMP] Fix test incompatibility with 32-bit platformsAlexey Bataev2015-09-101-2/+2
| | | | llvm-svn: 247255
* [ARM] Do not use vtrn for vectorshuffle if the order is reversedJames Molloy2015-09-104-4/+63
| | | | | | | | The tests in isVTRNMask and isVTRN_v_undef_Mask should also check that the elements of the upper and lower half of the vectorshuffle occur in the correct order when both halves are used. Without this test the code assumes that it is correct to use vector transpose (vtrn) for the masks <1, 1, 0, 0> and <1, 3, 0, 2>, among others, but the transpose actually incorrectly generates shuffles for <0, 0, 1, 1> and <0, 2, 1, 3> in this case. Patch by Jeroen Ketema! llvm-svn: 247254
* [ADT] Apply a large hammer to StringRef functions: attribute always_inline.Chandler Carruth2015-09-101-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The logic of this follows something Howard does in libc++ and something I discussed with Chris eons ago -- for a lot of functions, there is really no benefit to preserving "debug information" by leaving the out-of-line even in debug builds. This is especially true as we now do a very good job of preserving most debug information even in the face of inlining. There are a bunch of methods in StringRef that we are paying a completely unacceptable amount for with every debug build of every LLVM developer. Some day, we should fix Clang/LLVM so that developers can reasonable use a default of something other than '-O0' and not waste their lives waiting on *completely* unoptimized code to execute. We should have a default that doesn't impede debugging while providing at least plausable performance. But today is not that day. So today, I'm applying always_inline to the functions that are really hurting the critical path for stuff like 'check_llvm'. I'm being very cautious here, but there are a few other APIs that we really should do this for as a matter of pragmatism. Hopefully we can rip this out some day. With this change, TripleTest.Normalization runtime decreases by over 10%, and the total 'check-llvm' time on my 48-core box goes from 38s to just under 37s. llvm-svn: 247253
* [Support] Fix the always_inline attribute macro to not include theChandler Carruth2015-09-101-1/+1
| | | | | | | | 'inline' specifier. That specifier may or may not be valid for a given function, or it may be required for correct linkage even when the compiler doesn't support the always_inline attribute. llvm-svn: 247252
* [OPENMP] Outlined function for parallel and other regions with list of ↵Alexey Bataev2015-09-1031-616/+542
| | | | | | | | | captured variables. Currently all variables used in OpenMP regions are captured into a record and passed to outlined functions in this record. It may result in some poor performance because of too complex analysis later in optimization passes. Patch makes to emit outlined functions for parallel-based regions with a list of captured variables. It reduces code for 2*n GEPs, stores and loads at least. Codegen for task-based regions remains unchanged because runtime requires that all captured variables are passed in captured record. llvm-svn: 247251
* [ADT] Micro-optimize the Triple constructor by doing a single split andChandler Carruth2015-09-101-8/+21
| | | | | | | | | | | | re-using the resulting components rather than repeatedly splitting and re-splitting to compute each component as part of the initializer list. This is more work on PR23676. Sadly, it doesn't help much. It removes the constructor from my profile, but doesn't make a sufficient dent in the total time. But it should play together nicely with subsequent changes. llvm-svn: 247250
* [ADT] Fix a confusing interface spec and some annoying peculiaritiesChandler Carruth2015-09-103-33/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | with the StringRef::split method when used with a MaxSplit argument other than '-1' (which nobody really does today, but which should actually work). The spec claimed both to split up to MaxSplit times, but also to append <= MaxSplit strings to the vector. One of these doesn't make sense. Given the name "MaxSplit", let's go with it being a max over how many *splits* occur, which means the max on how many strings get appended is MaxSplit+1. I'm not actually sure the implementation correctly provided this logic either, as it used a really opaque loop structure. The implementation was also playing weird games with nullptr in the data field to try to rely on a totally opaque hidden property of the split method that returns a pair. Nasty IMO. Replace all of this with what is (IMO) simpler code that doesn't use the pair returning split method, and instead just finds each separator and appends directly. I think this is a lot easier to read, and it most definitely matches the spec. Added some tests that exercise the corner cases around StringRef() and StringRef("") that all now pass. I'll start using this in code in the next commit. llvm-svn: 247249
* [MS ABI] Select a pointer to member representation more oftenDavid Majnemer2015-09-104-1/+27
| | | | | | | | | Given a reference to a pointer to member whose class's inheritance model is unspecified, make sure we come up with an inheritance model in plausible places. One place we were missing involved LValue to RValue conversion, another involved unary type traits. llvm-svn: 247248
* GlobalsAAResult(&&): Move every members.NAKAMURA Takumi2015-09-101-1/+6
| | | | | | Or, one of MSVC builders failed with unexpected behavior. llvm-svn: 247247
* Added isUndef() interface for SDNodeElena Demikhovsky2015-09-101-0/+7
| | | | | | Differential Revision: http://reviews.llvm.org/D12720 llvm-svn: 247246
* [ADT] Switch a bunch of places in LLVM that were doing single-characterChandler Carruth2015-09-109-16/+16
| | | | | | | splits to actually use the single character split routine which does less work, and in a debug build is *substantially* faster. llvm-svn: 247245
* [ADT] Add a single-character version of the small vector split routineChandler Carruth2015-09-104-1/+43
| | | | | | | | | | | on StringRef. Finding and splitting on a single character is substantially faster than doing it on even a single character StringRef -- we immediately get to a *very* tuned memchr call this way. Even nicer, we get to this even in a debug build, shaving 18% off the runtime of TripleTest.Normalization, helping PR23676 some more. llvm-svn: 247244
* Add a way to skip the Go bindings tests even when Go is configured inChandler Carruth2015-09-104-0/+6
| | | | | | | | | | | | | CMake. The Go bindings tests in an unoptimized build take over 30 seconds for me, making it the slowest test in 'check-llvm' by a factor of two. I've only rigged this up fully to the CMake build. If someone is interested in rigging it up to the autoconf build, they're welcome to do so. llvm-svn: 247243
* [ScalarEvolution] Fix PR24757.Sanjoy Das2015-09-102-2/+77
| | | | | | | | | | | | | | | | | | | Summary: PR24757 was caused by some incorect math in `ScalarEvolution::HowFarToZero` -- the smallest unsigned solution for X in 2^N * A = 2^N * X is not necessarily A. Reviewers: atrick, majnemer, meheff Subscribers: llvm-commits, sanjoy Differential Revision: http://reviews.llvm.org/D12721 llvm-svn: 247242
* [LPM] Simplify this code and fix a compile error for compilers thatChandler Carruth2015-09-101-3/+1
| | | | | | | | don't correctly implement the scoping rules of C++11 range based for loops. This kind of aliasing isn't a good idea anyways (and wasn't really intended). llvm-svn: 247241
OpenPOWER on IntegriCloud