Skip to content
  1. Jul 17, 2009
  2. Jul 16, 2009
  3. Jul 15, 2009
  4. Jul 14, 2009
  5. Jul 13, 2009
  6. Jul 11, 2009
    • Daniel Dunbar's avatar
      Fix type conversion of ObjCObjectPointerType. · 7e5f0527
      Daniel Dunbar authored
       - Previous code was based on a misunderstanding (on my part) of the type
         representation.
      
      llvm-svn: 75385
      7e5f0527
    • Daniel Dunbar's avatar
      Generate correct prototype for objc_enumerationMutation. · 9d82da40
      Daniel Dunbar authored
       - This was a latent bug exposed by the recent objc type changes.
      
      llvm-svn: 75383
      9d82da40
    • Eli Friedman's avatar
      Fix typo (found by gcc warning). · 55179ca5
      Eli Friedman authored
      llvm-svn: 75325
      55179ca5
    • Steve Naroff's avatar
      This patch includes a conceptually simple, but very intrusive/pervasive change. · 7cae42b0
      Steve Naroff authored
      The idea is to segregate Objective-C "object" pointers from general C pointers (utilizing the recently added ObjCObjectPointerType). The fun starts in Sema::GetTypeForDeclarator(), where "SomeInterface *" is now represented by a single AST node (rather than a PointerType whose Pointee is an ObjCInterfaceType). Since a significant amount of code assumed ObjC object pointers where based on C pointers/structs, this patch is very tedious. It should also explain why it is hard to accomplish this in smaller, self-contained patches.
      
      This patch does most of the "heavy lifting" related to moving from PointerType->ObjCObjectPointerType. It doesn't include all potential "cleanups". The good news is additional cleanups can be done later (some are noted in the code). This patch is so large that I didn't want to include any changes that are purely aesthetic.
      
      By making the ObjC types truly built-in, they are much easier to work with (and require fewer "hacks"). For example, there is no need for ASTContext::isObjCIdStructType() or ASTContext::isObjCClassStructType()! We believe this change (and the follow-up cleanups) will pay dividends over time. 
      
      Given the amount of code change, I do expect some fallout from this change (though it does pass all of the clang tests). If you notice any problems, please let us know asap! Thanks.
      
      llvm-svn: 75314
      7cae42b0
  7. Jul 10, 2009
  8. Jul 08, 2009
  9. Jul 06, 2009
  10. Jul 03, 2009
Loading