Skip to content
  1. Apr 21, 2012
  2. Apr 20, 2012
    • Anna Zaks's avatar
      [analyzer] Run remove dead bindings right before leaving a function. · 7e53bd6f
      Anna Zaks authored
      This is needed to ensure that we always report issues in the correct
      function. For example, leaks are identified when we call remove dead
      bindings. In order to make sure we report a callee's leak in the callee,
      we have to run the operation in the callee's context.
      
      This change required quite a bit of infrastructure work since:
       - We used to only run remove dead bindings before a given statement;
      here we need to run it after the last statement in the function. For
      this, we added additional Program Point and special mode in the
      SymbolReaper to remove all symbols in context lower than the current
      one.
       - The call exit operation turned into a sequence of nodes, which are
      now guarded by CallExitBegin and CallExitEnd nodes for clarity and
      convenience.
      
      (Sorry for the long diff.)
      
      llvm-svn: 155244
      7e53bd6f
    • Anna Zaks's avatar
      [analyzer] Remove unused method. · 20492bf0
      Anna Zaks authored
      llvm-svn: 155243
      20492bf0
    • Anna Zaks's avatar
      [analyzer] Constify · 503ad9e9
      Anna Zaks authored
      llvm-svn: 155242
      503ad9e9
    • Bill Wendling's avatar
      If we discover all of the named structs in a module, then don't bother to · c5fae47a
      Bill Wendling authored
      process any more Values.
      
      llvm-svn: 155241
      c5fae47a
    • Jakob Stoklund Olesen's avatar
      Print <def,read-undef> to avoid confusion. · 7111a630
      Jakob Stoklund Olesen authored
      The <undef> flag on a def operand only applies to partial register
      redefinitions. Only print the flag when relevant, and print it as
      <def,read-undef> to make it clearer what it means.
      
      llvm-svn: 155239
      7111a630
    • Jim Ingham's avatar
      Make sure the "synchronous breakpoint callbacks" get called before the thread... · 6d66ce67
      Jim Ingham authored
      Make sure the "synchronous breakpoint callbacks" get called before the thread plan logic gets invoked, and if they
      ask to continue that should short-circuit the thread plans for that thread.  Also add a bit more explanation for
      how this machinery is supposed to work.  
      Also pass eExecutionPolicyOnlyWhenNeeded, not eExecutionPolicyAlways when evaluating the expression for breakpoint
      conditions.
      
      llvm-svn: 155236
      6d66ce67
    • Andrew Trick's avatar
      Added TargetRegisterInfo::getRegPressureSetName. · 1b422809
      Andrew Trick authored
      llvm-svn: 155235
      1b422809
    • Andrew Trick's avatar
      TableGen'd RegPressure: Added getPressureSetName. · 03eaaf5b
      Andrew Trick authored
      llvm-svn: 155234
      03eaaf5b
    • Greg Clayton's avatar
      Added logging so we can see when we are trying to complete a forward type and... · 9bbddbf8
      Greg Clayton authored
      Added logging so we can see when we are trying to complete a forward type and pull in the world. This is due to a compiler bug we are tracking (<rdar://problem/11291658>) where forward decls to classes and types are not properly scoped in namespaces, which results in the current LLDB looking for a type it will find many times in the accelerator tables, but never match. For example, when debugging with clang we get a forward decl like:
      
      class AnalysisResolver;
      
      And we will look for it everywhere and find many many matches, but the decl context of those matching DIEs is "clang::AnalysisResolver", so we never match anything, yet we pull in waaayyy too much DWARF in the process.
      
      To enable this logging enable the "lookups" category in the "dwarf" log channel:
      
      (lldb) log enable dwarf lookups
      
      llvm-svn: 155233
      9bbddbf8
    • Richard Smith's avatar
      Update doxygen comment to match changes in r155218. · 91adf295
      Richard Smith authored
      llvm-svn: 155232
      91adf295
    • Bill Wendling's avatar
      Modify the sh-bang to run out-of-the-box for FreeBSDes. · d63dcde1
      Bill Wendling authored
      llvm-svn: 155230
      d63dcde1
    • Andrew Trick's avatar
      New and improved comment. · 51ee9361
      Andrew Trick authored
      llvm-svn: 155229
      51ee9361
    • Andrew Trick's avatar
      SparseSet: Add support for key-derived indexes and arbitrary key types. · 1eb4a0da
      Andrew Trick authored
      This nicely handles the most common case of virtual register sets, but
      also handles anticipated cases where we will map pointers to IDs.
      
      The goal is not to develop a completely generic SparseSet
      template. Instead we want to handle the expected uses within llvm
      without any template antics in the client code. I'm adding a bit of
      template nastiness here, and some assumption about expected usage in
      order to make the client code very clean.
      
      The expected common uses cases I'm designing for:
      - integer keys that need to be reindexed, and may map to additional
        data
      - densely numbered objects where we want pointer keys because no
        number->object map exists.
      
      llvm-svn: 155227
      1eb4a0da
Loading