summaryrefslogtreecommitdiffstats
path: root/llvm
Commit message (Collapse)AuthorAgeFilesLines
...
* add missing tests for powi expansion with size optimizationsSanjay Patel2015-08-111-0/+27
| | | | | | The minsize test will be fixed in the next commit. llvm-svn: 244630
* fixed to use FileCheckSanjay Patel2015-08-111-5/+15
| | | | llvm-svn: 244627
* fixed to test attribute, rather than CPUSanjay Patel2015-08-111-1/+1
| | | | llvm-svn: 244625
* Enable EliminateAvailableExternally pass in the LTO pipeline.Teresa Johnson2015-08-111-0/+3
| | | | | | | | | | | | | | | Summary: For LTO we need to enable this pass in the LTO pipeline, as it is skipped during the "-flto -c" compile step (when PrepareForLTO is set). Reviewers: rnk Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D11919 llvm-svn: 244622
* Revert "Add non-member begin and end so that drop_begin works on ↵Rafael Espindola2015-08-111-10/+0
| | | | | | | | | | iterator_range." This reverts commit r244620. MSVC doesn't like it :-( llvm-svn: 244621
* Add non-member begin and end so that drop_begin works on iterator_range.Rafael Espindola2015-08-111-0/+10
| | | | llvm-svn: 244620
* fix typos; NFCSanjay Patel2015-08-111-1/+1
| | | | llvm-svn: 244619
* Variable names should start with an upper case letter; NFCSanjay Patel2015-08-111-9/+9
| | | | llvm-svn: 244618
* fix minsize detection: minsize attribute implies optimizing for sizeSanjay Patel2015-08-112-14/+39
| | | | llvm-svn: 244617
* [GlobalMerge] Use private linkage for MergedGlobals variablesJohn Brawn2015-08-1111-91/+62
| | | | | | | | | | | | | | | Other objects can never reference the MergedGlobals symbol so external linkage is never needed. Using private instead of internal linkage means the object is more similar to what it looks like when global merging is not enabled, with the only difference being that the merged variables are addressed indirectly relative to the start of the section they are in. Also add aliases for merged variables with internal linkage, as this also makes the object be more like what it is when they are not merged. Differential Revision: http://reviews.llvm.org/D11942 llvm-svn: 244615
* Fix InstCombine test: invalid CHECK line slipped in r231270Mehdi Amini2015-08-111-1/+2
| | | | | | | | | | | | | | I incorrectly wrote CHECK-NEXT with followin with ':', the check was ignored by FileCheck. The non-inbound GEP is folded here because the DataLayout is no longer optional, the fold was originally guarded with a comment that said: We need TD information to know the pointer size unless this is inbounds. Now we always have "TD information" and perform the fold. Thanks Jonathan Roelofs for noticing. From: Mehdi Amini <mehdi.amini@apple.com> llvm-svn: 244613
* remove unnecessary settings/attributes from test caseSanjay Patel2015-08-111-6/+6
| | | | llvm-svn: 244612
* [RegionInfo] Verify getRegionForMichael Kruse2015-08-112-0/+27
| | | | | | | | | | | | | | | Summary: Check the contents of BBtoRegion during analysis verification. It only takes place if -verify-region-info is passed or LLVM is compiled with XDEBUG. RegionBase<Tr>::verifyRegion() also checks the RegionInfoBase<Tr>::VerifyRegionInfo flag, which is redundant, but verifyRegion() is public API and might be invoked from other sites. In order to avoid behavioral change, this check is not removed. In any case, no region will be verified unless VerifyRegionInfo is set. Reviewers: grosser Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D11872 llvm-svn: 244611
* fix code that was accidentally commented out in previous commitSanjay Patel2015-08-111-2/+2
| | | | llvm-svn: 244610
* fix typos in comments; NFCSanjay Patel2015-08-111-5/+5
| | | | llvm-svn: 244609
* fix typo in comment; NFCSanjay Patel2015-08-111-1/+1
| | | | llvm-svn: 244607
* delete FIXME comment; it's fixedSanjay Patel2015-08-111-2/+0
| | | | llvm-svn: 244605
* fix minsize detection: minsize attribute implies optimizing for sizeSanjay Patel2015-08-112-7/+6
| | | | llvm-svn: 244604
* add missing test for machine combiner when optimizing for sizeSanjay Patel2015-08-111-0/+30
| | | | | | The minsize test will be fixed in the next commit. llvm-svn: 244603
* [X86] Allow merging of immediates within a basic block for code size savingsMichael Kuperstein2015-08-115-92/+199
| | | | | | | | | | | First step in preventing immediates that occur more than once within a single basic block from being pulled into their users, in order to prevent unnecessary large instruction encoding .Currently enabled only when optimizing for size. Patch by: zia.ansari@intel.com Differential Revision: http://reviews.llvm.org/D11363 llvm-svn: 244601
* [AArch64] Match fminnum/fmaxnum for vector fminnm/fmaxnm instead of an ↵James Molloy2015-08-114-19/+37
| | | | | | | | | | | intrinsic. Lower Intrinsic::aarch64_neon_fmin/fmax to fminnum/fmannum and match that instead. Minimal functional change: - Extra tests added because coverage of scalar fminnm/fmaxnm instructions was nonexistant. - f16 test updated because now we actually generate scalar fminnm/fmaxnm we no longer need to bail out to a libcall! llvm-svn: 244595
* [AArch64] Replace the custom AArch64ISD::FMIN/MAX nodes with ISD::FMINNAN/MAXNANJames Molloy2015-08-113-19/+15
| | | | | | NFCI. This just removes custom ISDNodes that are no longer needed. llvm-svn: 244594
* [ARM] Match fminnan/fmaxnan for vector vmin/vmax instead of an intrinsicJames Molloy2015-08-112-4/+20
| | | | | | | | Lower Intrinsic::arm_neon_vmins/vmaxs to fminnan/fmaxnan and match that instead. This is important because SDAG will soon be able to select FMINNAN itself, so we need a unified lowering path for intrinsics and SDAG. NFCI. llvm-svn: 244593
* [ARM] Match fminnum/fmaxnum for vector vminnm/vmaxnm instead of an intrinsicJames Molloy2015-08-112-4/+16
| | | | | | | | Lower the intrinsic to a FMINNUM/FMAXNUM node and select that instead. This is important because soon SDAG will be able to select FMINNUM/FMAXNUM itself, so we need an integrated lowering path between SDAG and intrinsics. NFCI. llvm-svn: 244592
* [ARM] Replace ARMISD::VMINNM/VMAXNM with ISD::FMINNUM/FMAXNUMJames Molloy2015-08-114-18/+10
| | | | | | NFCI. This replaces another custom ISDNode with a generic equivalent. llvm-svn: 244591
* [ARM] Replace ARMISD::FMIN/FMAX with the shiny new ISD::FMINNAN/FMAXNAN.James Molloy2015-08-113-13/+12
| | | | | | NFCI. This removes a custom ISDNode. llvm-svn: 244590
* Revert r244516; it was causing cmake configuration failures on Windows with ↵Aaron Ballman2015-08-111-4/+5
| | | | | | | | Visual Studio. http://bb.pgr.jp/builders/msbuild-llvmclang-x64-msc18-DA/builds/475 llvm-svn: 244589
* [X86] Add SAL mnemonics for Intel syntaxMarina Yatsina2015-08-112-0/+4
| | | | | | | | SAL and SHL instructions perform the same operation Differential Revision: http://reviews.llvm.org/D11882 llvm-svn: 244588
* [X86] Fix REPE, REPZ, REPNZ for intel syntaxMarina Yatsina2015-08-112-3/+16
| | | | | | | | | REPE, REPZ, REPNZ, REPNE should have mnemonics for Intel syntax as well. Currently using these instructions causes compilation errors for Intel syntax. Differential Revision: http://reviews.llvm.org/D11794 llvm-svn: 244584
* [X86] Fix imul alias for intel syntaxMarina Yatsina2015-08-112-6/+13
| | | | | | | | | The "imul reg, imm" alias is not defined for intel syntax. In intel syntax there is no w/l/q suffix for the imul instruction. Differential Revision: http://reviews.llvm.org/D11887 llvm-svn: 244582
* Add new ISD nodes: ISD::FMINNAN and ISD::FMAXNANJames Molloy2015-08-117-0/+24
| | | | | | | | | | | | | | | | | | The intention of these is to be a corollary to ISD::FMINNUM/FMAXNUM, differing only on how NaNs are treated. FMINNUM returns the non-NaN input (when given one NaN and one non-NaN), FMINNAN returns the NaN input instead. This patch includes support for scalarizing, widening and splitting vectors, but not expansion or softening. The reason is that these should never be needed - FMINNAN nodes are only going to be created in one place (SDAGBuilder::visitSelect) and there we'll check if the node is legal or custom. I could preemptively add expand and soften code, but I'm fairly opposed to adding code I can't test. It's bad enough I can't create tests with this patch, but at least this code will be exercised by the ARM and AArch64 backends fairly shortly. llvm-svn: 244581
* Add support for floating-point minnum and maxnumJames Molloy2015-08-119-52/+502
| | | | | | | | | | | | | | | | | The select pattern recognition in ValueTracking (as used by InstCombine and SelectionDAGBuilder) only knew about integer patterns. This teaches it about minimum and maximum operations. matchSelectPattern() has been extended to return a struct containing the existing Flavor and a new enum defining the pattern's behavior when given one NaN operand. C minnum() is defined to return the non-NaN operand in this case, but the idiomatic C "a < b ? a : b" would return the NaN operand. ARM and AArch64 at least have different instructions for these different cases. llvm-svn: 244580
* [mips] Remap move as or.Vasileios Kalintiris2015-08-1147-53/+120
| | | | | | | | | | | | | | | | | | | | | | | | Summary: This patch remaps the assembly idiom 'move' to 'or' instead of 'daddu' or 'addu'. The use of addu/daddu instead of or as move was highlighted as a performance issue during the analysis of a recent 64bit design. Originally move was encoded as 'or' by binutils but was changed for the r10k cpu family due to their pipeline which had 2 arithmetic units and a single logical unit, and so could issue multiple (d)addu based moves at the same time but only 1 logical move. This patch preserves the disassembly behaviour so that disassembling a old style (d)addu move still appears as move, but assembling move always gives an or Patch by Simon Dardis. Reviewers: vkalintiris Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D11796 llvm-svn: 244579
* [X86] When optimizing for minsize, use POP for small post-call stack clean-upMichael Kuperstein2015-08-114-3/+136
| | | | | | | | | | | | | | | | When optimizing for size, replace "addl $4, %esp" and "addl $8, %esp" following a call by one or two pops, respectively. We don't try to do it in general, but only when the stack adjustment immediately follows a call - which is the most common case. That allows taking a short-cut when trying to find a free register to pop into, instead of a full-blown liveness check. If the adjustment immediately follows a call, then every register the call clobbers but doesn't define should be dead at that point, and can be used. Differential Revision: http://reviews.llvm.org/D11749 llvm-svn: 244578
* Allow PeepholeOptimizer to fold a few more casesMichael Kuperstein2015-08-113-18/+14
| | | | | | | | | | The condition for clearing the folding candidate list was clamped together with the "uninteresting instruction" condition. This is too conservative, e.g. we don't need to clear the list when encountering an IMPLICIT_DEF. Differential Revision: http://reviews.llvm.org/D11591 llvm-svn: 244577
* [GMR] Be a bit smarter about which globals don't alias when doing recursive ↵Michael Kuperstein2015-08-112-11/+30
| | | | | | | | | | lookups Should hopefully fix the remainder of PR24288. Differential Revision: http://reviews.llvm.org/D11900 llvm-svn: 244575
* [RuntimeDyld][AArch64] Add explicit addends before calling relocationValueRef.Lang Hames2015-08-112-5/+16
| | | | | | relocationValueRef uses the addend, so it has to be set before the call. llvm-svn: 244574
* Enable five passing dsymutil tests on Windows. Yaron Keren2015-08-115-5/+0
| | | | | | | These tests pass with Windows 7 x64 + MSYS2. I'll see if the bots like them as well and disable the failing ones. llvm-svn: 244572
* Fix unused variable 'X' in release builds.Nick Lewycky2015-08-111-0/+2
| | | | llvm-svn: 244571
* WebAssembly: NFC fix release build break, unused variable.JF Bastien2015-08-111-0/+1
| | | | | | | | | | Summary: Caused by D11914, pointed out by blaikie. Subscribers: llvm-commits, jfb, dblaikie Differential Revision: http://reviews.llvm.org/D11929 llvm-svn: 244570
* [libFuzzer] fix docs buildKostya Serebryany2015-08-111-5/+13
| | | | llvm-svn: 244566
* [IR] Verify EH pad predecessorsDavid Majnemer2015-08-112-20/+95
| | | | | | | Make sure that an EH pad's predecessors are using their unwind edge to transfer control to the EH pad. llvm-svn: 244563
* WebAssembly: add basic floating-point testsJF Bastien2015-08-113-4/+146
| | | | | | | | | | Summary: I somehow forgot to add these when I added the basic floating-point opcodes. Also remove ceil/floor/trunc/nearestint for now, and add them only when properly tested. Subscribers: llvm-commits, sunfish, jfb Differential Revision: http://reviews.llvm.org/D11927 llvm-svn: 244562
* [libFuzzer] add the list of trophies to the docs. It is incomplete, ↵Kostya Serebryany2015-08-111-0/+15
| | | | | | additions are welcome :) llvm-svn: 244560
* [libFuzzer] add -only_ascii flagKostya Serebryany2015-08-116-2/+29
| | | | llvm-svn: 244559
* [WinEHPrepare] Add rudimentary support for the new EH instructionsDavid Majnemer2015-08-112-9/+374
| | | | | | | | | | | | | | | | | | This adds somewhat basic preparation functionality including: - Formation of funclets via coloring basic blocks. - Cloning of polychromatic blocks to ensure that funclets have unique program counters. - Demotion of values used between different funclets. - Some amount of cleanup once we have removed predecessors from basic blocks. - Verification that we are left with a CFG that makes some amount of sense. N.B. Arguments and numbering still need to be done. Differential Revision: http://reviews.llvm.org/D11750 llvm-svn: 244558
* Explicitly clear the MI operand list when getInstruction() is called. Call ↵Cameron Esfahani2015-08-115-22/+3
| | | | | | | | | | | | | | MI.clear() within MCD::OPC_Decode case and inside of translateInstruction() for the X86 target. Remove now unnecessary MI.clear() from ARMDisassembler. Summary: Explicitly clear the MI operand list when getInstruction() is called. Reviewers: hfinkel, t.p.northover, hvarga, kparzysz, jyknight, qcolombet, uweigand Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D11665 llvm-svn: 244557
* Print vectorization analysis when loop hint is specified.Tyler Nowicki2015-08-116-21/+44
| | | | | | This patch and a relatec clang patch solve the problem of having to explicitly enable analysis when specifying a loop hint pragma to get the diagnostics. Passing AlwasyPrint as the pass name (see below) causes the front-end to print the diagnostic if the user has specified '-Rpass-analysis' without an '=<target-pass>’. Users of loop hints can pass that compiler option without having to specify the pass and they will get diagnostics for only those loops with loop hints. llvm-svn: 244555
* Update the syntax for load instruction in this example.Nick Lewycky2015-08-111-1/+1
| | | | llvm-svn: 244554
* Moved LoopVectorizeHints and related functions before ↵Tyler Nowicki2015-08-111-270/+270
| | | | | | LoopVectorizationLegality and LoopVectorizationCostModel. llvm-svn: 244552
OpenPOWER on IntegriCloud