Skip to content
  1. Apr 06, 2012
    • Chandler Carruth's avatar
      Sink the collection of return instructions until after *all* · 49da9339
      Chandler Carruth authored
      simplification has been performed. This is a bit less efficient
      (requires another ilist walk of the basic blocks) but shouldn't matter
      in practice. More importantly, it's just too much work to keep track of
      all the various ways the return instructions can be mutated while
      simplifying them. This fixes yet another crasher, reported by Daniel
      Dunbar.
      
      llvm-svn: 154179
      49da9339
    • Chandler Carruth's avatar
      Sink the return instruction collection until after we're done deleting · e41f6f41
      Chandler Carruth authored
      dead code, including dead return instructions in some cases. Otherwise,
      we end up having a bogus poniter to a return instruction that blows up
      much further down the road.
      
      It turns out that this pattern is both simpler to code, easier to update
      in the face of enhancements to the inliner cleanup, and likely cheaper
      given that it won't add dead instructions to the list.
      
      Thanks to John Regehr's numerous test cases for teasing this out.
      
      llvm-svn: 154157
      e41f6f41
  2. Mar 28, 2012
  3. Mar 25, 2012
    • Chandler Carruth's avatar
      Teach the function cloner (and thus the inliner) to simplify PHINodes · ef82cf5b
      Chandler Carruth authored
      aggressively. There are lots of dire warnings about this being expensive
      that seem to predate switching to the TrackingVH-based value remapper
      that is automatically updated on RAUW. This makes it easy to not just
      prune single-entry PHIs, but to fully simplify PHIs, and to recursively
      simplify the newly inlined code to propagate PHINode simplifications.
      
      This introduces a bit of a thorny problem though. We may end up
      simplifying a branch condition to a constant when we fold PHINodes, and
      we would like to nuke any dead blocks resulting from this so that time
      isn't wasted continually analyzing them, but this isn't easy. Deleting
      basic blocks *after* they are fully cloned and mapped into the new
      function currently requires manually updating the value map. The last
      piece of the simplification-during-inlining puzzle will require either
      switching to WeakVH mappings or some other piece of refactoring. I've
      left a FIXME in the testcase about this.
      
      llvm-svn: 153410
      ef82cf5b
    • Chandler Carruth's avatar
      Move the instruction simplification of callsite arguments in the inliner · 21211992
      Chandler Carruth authored
      to instead rely on much more generic and powerful instruction
      simplification in the function cloner (and thus inliner).
      
      This teaches the pruning function cloner to use instsimplify rather than
      just the constant folder to fold values during cloning. This can
      simplify a large number of things that constant folding alone cannot
      begin to touch. For example, it will realize that 'or' and 'and'
      instructions with certain constant operands actually become constants
      regardless of what their other operand is. It also can thread back
      through the caller to perform simplifications that are only possible by
      looking up a few levels. In particular, GEPs and pointer testing tend to
      fold much more heavily with this change.
      
      This should (in some cases) have a positive impact on compile times with
      optimizations on because the inliner itself will simply avoid cloning
      a great deal of code. It already attempted to prune proven-dead code,
      but now it will be use the stronger simplifications to prove more code
      dead.
      
      llvm-svn: 153403
      21211992
  4. Mar 21, 2012
  5. Mar 08, 2012
    • Stepan Dyatkovskiy's avatar
      Taken into account Duncan's comments for r149481 dated by 2nd Feb 2012: · 5b648afb
      Stepan Dyatkovskiy authored
      http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136146.html
      
      Implemented CaseIterator and it solves almost all described issues: we don't need to mix operand/case/successor indexing anymore. Base iterator class is implemented as a template since it may be initialized either from "const SwitchInst*" or from "SwitchInst*".
      
      ConstCaseIt is just a read-only iterator.
      CaseIt is read-write iterator; it allows to change case successor and case value.
      
      Usage of iterator allows totally remove resolveXXXX methods. All indexing convertions done automatically inside the iterator's getters.
      
      Main way of iterator usage looks like this:
      SwitchInst *SI = ... // intialize it somehow
      
      for (SwitchInst::CaseIt i = SI->caseBegin(), e = SI->caseEnd(); i != e; ++i) {
        BasicBlock *BB = i.getCaseSuccessor();
        ConstantInt *V = i.getCaseValue();
        // Do something.
      }
      
      If you want to convert case number to TerminatorInst successor index, just use getSuccessorIndex iterator's method.
      If you want initialize iterator from TerminatorInst successor index, use CaseIt::fromSuccessorIndex(...) method.
      
      There are also related changes in llvm-clients: klee and clang.
      
      llvm-svn: 152297
      5b648afb
  6. Feb 06, 2012
  7. Feb 01, 2012
    • Stepan Dyatkovskiy's avatar
      SwitchInst refactoring. · 513aaa56
      Stepan Dyatkovskiy authored
      The purpose of refactoring is to hide operand roles from SwitchInst user (programmer). If you want to play with operands directly, probably you will need lower level methods than SwitchInst ones (TerminatorInst or may be User). After this patch we can reorganize SwitchInst operands and successors as we want.
      
      What was done:
      
      1. Changed semantics of index inside the getCaseValue method:
      getCaseValue(0) means "get first case", not a condition. Use getCondition() if you want to resolve the condition. I propose don't mix SwitchInst case indexing with low level indexing (TI successors indexing, User's operands indexing), since it may be dangerous.
      2. By the same reason findCaseValue(ConstantInt*) returns actual number of case value. 0 means first case, not default. If there is no case with given value, ErrorIndex will returned.
      3. Added getCaseSuccessor method. I propose to avoid usage of TerminatorInst::getSuccessor if you want to resolve case successor BB. Use getCaseSuccessor instead, since internal SwitchInst organization of operands/successors is hidden and may be changed in any moment.
      4. Added resolveSuccessorIndex and resolveCaseIndex. The main purpose of these methods is to see how case successors are really mapped in TerminatorInst.
      4.1 "resolveSuccessorIndex" was created if you need to level down from SwitchInst to TerminatorInst. It returns TerminatorInst's successor index for given case successor.
      4.2 "resolveCaseIndex" converts low level successors index to case index that curresponds to the given successor.
      
      Note: There are also related compatability fix patches for dragonegg, klee, llvm-gcc-4.0, llvm-gcc-4.2, safecode, clang.
      llvm-svn: 149481
      513aaa56
  8. Dec 23, 2011
  9. Oct 21, 2011
  10. Oct 02, 2011
  11. Jul 19, 2011
  12. Jul 12, 2011
    • Jay Foad's avatar
      Second attempt at de-constifying LLVM Types in FunctionType::get(), · b804a2b7
      Jay Foad authored
      StructType::get() and TargetData::getIntPtrType().
      
      llvm-svn: 134982
      b804a2b7
    • Bill Wendling's avatar
      Revert r134893 and r134888 (and related patches in other trees). It was causing · a78cd228
      Bill Wendling authored
      an assert on Darwin llvm-gcc builds.
      
      Assertion failed: (castIsValid(op, S, Ty) && "Invalid cast!"), function Create, file /Users/buildslave/zorg/buildbot/smooshlab/slave-0.8/build.llvm-gcc-i386-darwin9-RA/llvm.src/lib/VMCore/Instructions.cpp, li\
      ne 2067.
      etc.
      
      http://smooshlab.apple.com:8013/builders/llvm-gcc-i386-darwin9-RA/builds/2354
      
      --- Reverse-merging r134893 into '.':
      U    include/llvm/Target/TargetData.h
      U    include/llvm/DerivedTypes.h
      U    tools/bugpoint/ExtractFunction.cpp
      U    unittests/Support/TypeBuilderTest.cpp
      U    lib/Target/ARM/ARMGlobalMerge.cpp
      U    lib/Target/TargetData.cpp
      U    lib/VMCore/Constants.cpp
      U    lib/VMCore/Type.cpp
      U    lib/VMCore/Core.cpp
      U    lib/Transforms/Utils/CodeExtractor.cpp
      U    lib/Transforms/Instrumentation/ProfilingUtils.cpp
      U    lib/Transforms/IPO/DeadArgumentElimination.cpp
      U    lib/CodeGen/SjLjEHPrepare.cpp
      --- Reverse-merging r134888 into '.':
      G    include/llvm/DerivedTypes.h
      U    include/llvm/Support/TypeBuilder.h
      U    include/llvm/Intrinsics.h
      U    unittests/Analysis/ScalarEvolutionTest.cpp
      U    unittests/ExecutionEngine/JIT/JITTest.cpp
      U    unittests/ExecutionEngine/JIT/JITMemoryManagerTest.cpp
      U    unittests/VMCore/PassManagerTest.cpp
      G    unittests/Support/TypeBuilderTest.cpp
      U    lib/Target/MBlaze/MBlazeIntrinsicInfo.cpp
      U    lib/Target/Blackfin/BlackfinIntrinsicInfo.cpp
      U    lib/VMCore/IRBuilder.cpp
      G    lib/VMCore/Type.cpp
      U    lib/VMCore/Function.cpp
      G    lib/VMCore/Core.cpp
      U    lib/VMCore/Module.cpp
      U    lib/AsmParser/LLParser.cpp
      U    lib/Transforms/Utils/CloneFunction.cpp
      G    lib/Transforms/Utils/CodeExtractor.cpp
      U    lib/Transforms/Utils/InlineFunction.cpp
      U    lib/Transforms/Instrumentation/GCOVProfiling.cpp
      U    lib/Transforms/Scalar/ObjCARC.cpp
      U    lib/Transforms/Scalar/SimplifyLibCalls.cpp
      U    lib/Transforms/Scalar/MemCpyOptimizer.cpp
      G    lib/Transforms/IPO/DeadArgumentElimination.cpp
      U    lib/Transforms/IPO/ArgumentPromotion.cpp
      U    lib/Transforms/InstCombine/InstCombineCompares.cpp
      U    lib/Transforms/InstCombine/InstCombineAndOrXor.cpp
      U    lib/Transforms/InstCombine/InstCombineCalls.cpp
      U    lib/CodeGen/DwarfEHPrepare.cpp
      U    lib/CodeGen/IntrinsicLowering.cpp
      U    lib/Bitcode/Reader/BitcodeReader.cpp
      
      llvm-svn: 134949
      a78cd228
  13. Jul 11, 2011
  14. Jul 08, 2011
  15. Jun 23, 2011
  16. Jun 21, 2011
  17. Jun 20, 2011
    • Jay Foad's avatar
      Change how PHINodes store their operands. · e03c05c3
      Jay Foad authored
      Change PHINodes to store simple pointers to their incoming basic blocks,
      instead of full-blown Uses.
      
      Note that this loses an optimization in SplitCriticalEdge(), because we
      can no longer walk the use list of a BasicBlock to find phi nodes. See
      the comment I removed starting "However, the foreach loop is slow for
      blocks with lots of predecessors".
      
      Extend replaceAllUsesWith() on a BasicBlock to also update any phi
      nodes in the block's successors. This mimics what would have happened
      when PHINodes were proper Users of their incoming blocks. (Note that
      this only works if OldBB->replaceAllUsesWith(NewBB) is called when
      OldBB still has a terminator instruction, so it still has some
      successors.)
      
      llvm-svn: 133435
      e03c05c3
  18. Jan 08, 2011
    • Chris Lattner's avatar
      Revamp the ValueMapper interfaces in a couple ways: · 43f8d164
      Chris Lattner authored
      1. Take a flags argument instead of a bool.  This makes
         it more clear to the reader what it is used for.
      2. Add a flag that says that "remapping a value not in the
         map is ok".
      3. Reimplement MapValue to share a bunch of code and be a lot
         more efficient.  For lookup failures, don't drop null values
         into the map.
      4. Using the new flag a bunch of code can vaporize in LinkModules
         and LoopUnswitch, kill it.
      
      No functionality change.
      
      llvm-svn: 123058
      43f8d164
  19. Oct 13, 2010
  20. Aug 26, 2010
    • Dan Gohman's avatar
      Reapply r112091 and r111922, support for metadata linking, with a · ca26f790
      Dan Gohman authored
      fix: add a flag to MapValue and friends which indicates whether
      any module-level mappings are being made. In the common case of
      inlining, no module-level mappings are needed, so MapValue doesn't
      need to examine non-function-local metadata, which can be very
      expensive in the case of a large module with really deep metadata
      (e.g. a large C++ program compiled with -g).
      
      This flag is a little awkward; perhaps eventually it can be moved
      into the ClonedCodeInfo class.
      
      llvm-svn: 112190
      ca26f790
  21. Aug 24, 2010
  22. Jul 21, 2010
  23. Jun 24, 2010
  24. May 07, 2010
  25. Apr 21, 2010
  26. Mar 08, 2010
  27. Jan 27, 2010
  28. Jan 05, 2010
    • Devang Patel's avatar
      Remove dead debug info intrinsics. · be94f239
      Devang Patel authored
       Intrinsic::dbg_stoppoint
       Intrinsic::dbg_region_start 
       Intrinsic::dbg_region_end 
       Intrinsic::dbg_func_start
      AutoUpgrade simply ignores these intrinsics now.
      
      llvm-svn: 92557
      be94f239
  29. Dec 31, 2009
Loading