Skip to content
  1. Oct 08, 2012
  2. Oct 07, 2012
  3. Oct 06, 2012
    • Dmitri Gribenko's avatar
      List of potential checkers: smart pointer checker: actually, unique_ptr<T[]> · 67df63f6
      Dmitri Gribenko authored
      will do the right thing for new[] allocated memory.  Thanks David!
      
      llvm-svn: 165365
      67df63f6
    • Dmitri Gribenko's avatar
      Clang static analyzer docs: fix a couple of HTML markup issues and non-UTF-8 · 760cbe65
      Dmitri Gribenko authored
      characters.
      
      llvm-svn: 165364
      760cbe65
    • Dmitri Gribenko's avatar
      a124d76e
    • Benjamin Kramer's avatar
      Expose __builtin_bswap16. · a801f4a8
      Benjamin Kramer authored
      GCC has always supported this on PowerPC and 4.8 supports it on all platforms,
      so it's a good idea to expose it in clang too. LLVM supports this on all targets.
      
      llvm-svn: 165362
      a801f4a8
    • Ted Kremenek's avatar
      Place warn_impcast_different_enum_types in a new warning group,... · 68e2c7be
      Ted Kremenek authored
      Place warn_impcast_different_enum_types in a new warning group, -Wenum-conversion, that is a subgroup of -Wconversion.
      
      llvm-svn: 165361
      68e2c7be
    • Ted Kremenek's avatar
      Add link to potential future checkers. · 76b8ac46
      Ted Kremenek authored
      llvm-svn: 165360
      76b8ac46
    • Ted Kremenek's avatar
      Add list of potential checkers. Provided by Anton Yartsev! · 4bb7eb1c
      Ted Kremenek authored
      llvm-svn: 165359
      4bb7eb1c
    • Jordan Rose's avatar
      [analyzer] Tweak test to run the retain-count checker even on non-Darwin. · 69583bfe
      Jordan Rose authored
      This should fix the bots.
      
      llvm-svn: 165358
      69583bfe
    • Jason Molenda's avatar
      In DynamicLoaderDarwinKernel::OSKextLoadedKextSummary::LoadImageUsingMemoryModule(), · 53667f5d
      Jason Molenda authored
      if we have a kernel binary, set the target's architecture to match.
      
      Include the target's architecture in the ModuleSpec when we're searching for the 
      kext binaries on the local system -- otherwise we won't get a specific slice of
      a fat file picked out for us and we won't use the returned Module correctly.
      
      Remove the redundant attempt to find a file on the local filesystem from this method.
      
      
      In ProcessGDBRemote::CheckForKernel(), if we have a kernel binary in memory, mark
      the canJIT as false.  There is no jitting code in kernel debug sessions.
      
      llvm-svn: 165357
      53667f5d
    • Jason Molenda's avatar
      Revert Vishal's patch that Enrico commited, at least for the weekend. With it applied, · cc62f287
      Jason Molenda authored
      starting lldb I get
      
      % ./lldb -x
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
        File "/private/tmp/build/Debug/LLDB.framework/Versions/A/Resources/Python/lldb/__init__.py", line 9008
          raise TypeError("No array item of type %s" % str(type(key)))
              ^
      SyntaxError: invalid syntax
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      NameError: name 'run_one_line' is not defined
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      NameError: name 'run_one_line' is not defined
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      NameError: name 'run_one_line' is not defined
      (lldb)
      
      
      I did a clean build and still got the problem so I'm backing this out until Enrico can
      look at it.
      
      llvm-svn: 165356
      cc62f287
    • Jordan Rose's avatar
      ParentMap: Restore the ability to update an existing map. · adb5354c
      Jordan Rose authored
      The Clang ASTs are a DAG, not a pure tree. However, ParentMap has to
      choose a single parent for each object. In the main (only?) cases in
      which the AST forms a DAG, it protects from multiple traversal by using
      OpaqueValueExprs. Previously, ParentMap would just unconditionally look
      through all OpaqueValueExprs when building its map.
      
      In order to make this behavior better for the analyzer's diagnostics,
      ParentMap was changed to not set a statement's parent if there already
      was one in the map. However, ParentMap is supposed to allow updating
      existing mappings by calling addStmt once again. This change makes the
      "transparency" of OpaqueValueExprs explicit, and disables it when it
      is not desired, rather than checking the current contents of the map.
      
      This new code seems like a big change, but it should actually have
      essentially the same performance as before. Only OpaqueValueExprs and
      their users (PseudoObjectExpr and BinaryConditionalOperator) will
      have any different behavior.
      
      There should be no user-visible functionality change, though a test
      has been added for the current behavior of BinaryConditionalOperator
      source locations and accompanying Xcode arrows (which are not so great...).
      
      llvm-svn: 165355
      adb5354c
Loading