Skip to content
  1. Mar 23, 2010
  2. Mar 22, 2010
  3. Mar 21, 2010
    • Rafael Espindola's avatar
      Fix PR6618. · 568586ff
      Rafael Espindola authored
      If a struct has an invalid field, mark it as invalid. Also avoid producing
      errors about incomplete types that are invalid.
      
      llvm-svn: 99150
      568586ff
  4. Mar 20, 2010
  5. Mar 19, 2010
    • Douglas Gregor's avatar
      Remove the capture, serialization, and deserialization of comment · 9507d46d
      Douglas Gregor authored
      ranges as part of the ASTContext. This code is not and was never used,
      but contributes ~250k to the size of the Cocoa.h precompiled
      header.
      
      llvm-svn: 99007
      9507d46d
    • John McCall's avatar
      Promote enum types during -Wsign-compare. Fixes some spurious warnings, · ce5cbdc4
      John McCall authored
      mostly during conditional expressions.
      
      llvm-svn: 98975
      ce5cbdc4
    • Fariborz Jahanian's avatar
      Diagnose conversion of 'Class' to/from objective-c · d5bb8cb3
      Fariborz Jahanian authored
      object pointer types.
      Fixes radar 7634850.
      
      llvm-svn: 98970
      d5bb8cb3
    • John McCall's avatar
      Remember the "found declaration" for an overload candidate, which is the · a0296f79
      John McCall authored
      entity (if applicable) which was actually looked up.  If a candidate was found
      via a using declaration, this is the UsingShadowDecl;  otherwise, if
      the candidate is template specialization, this is the template;  otherwise,
      this is the function.
      
      The point of this exercise is that "found declarations" are the entities
      we do access control for, not their underlying declarations.  Broadly speaking,
      this patch fixes access control for using declarations.
      
      There is a *lot* of redundant code calling into the overload-resolution APIs;
      we really ought to clean that up.
      
      llvm-svn: 98945
      a0296f79
    • John McCall's avatar
      When elevating access along an inheritance path, initialize the computed · a332b953
      John McCall authored
      access to the (elevated) access of the accessed declaration, if applicable,
      rather than plunking that access onto the end after we've calculated the
      inheritance access.
      
      Also, being a friend of a derived class gives you public access to its
      members (subject to later modification by further inheritance);  it does
      not simply ignore a single location of restricted inheritance.
      
      Also, when computing the best unprivileged path to a subobject, preserve
      the information that the worst path might be AS_none (forbidden) rather
      than a minimum of AS_private.
      
      llvm-svn: 98899
      a332b953
  6. Mar 18, 2010
  7. Mar 17, 2010
  8. Mar 16, 2010
  9. Mar 15, 2010
Loading