Skip to content
  1. Oct 05, 2008
  2. Oct 03, 2008
  3. Oct 02, 2008
  4. Sep 30, 2008
  5. Sep 29, 2008
  6. Sep 28, 2008
  7. Sep 26, 2008
  8. Sep 25, 2008
  9. Sep 23, 2008
    • Daniel Dunbar's avatar
      Implement type checking of Objective-C property attributes. · e8a06e61
      Daniel Dunbar authored
       - readonly and readwrite are mutually exclusive.
       - assign, copy, and retain are mutually exclusive.
       - copy and retain are invalid on non-object types.
       - Warn about using default 'assign' property on object types
         (attempting to follow gcc behavior).
      
      llvm-svn: 56507
      e8a06e61
  10. Sep 22, 2008
  11. Sep 18, 2008
  12. Sep 17, 2008
  13. Sep 12, 2008
    • Daniel Dunbar's avatar
      Add --suppress-system-warnings (on by default, use =0 to disable) · 84b70f7f
      Daniel Dunbar authored
       - For investigating warnings in system headers / builtins.
       - Currently also enables the behavior that allows silent redefinition
         of types in system headers. Conceptually these are separate but I
         didn't feel it was worth two options (or changing LangOptions).
      
      llvm-svn: 56163
      84b70f7f
    • Douglas Gregor's avatar
      Give string literals const element typesin C++, and cope with the deprecated... · aa1e21dc
      Douglas Gregor authored
      Give string literals const element typesin C++, and cope with the deprecated C++ conversion from a string literal to a pointer-to-non-const-character
      
      llvm-svn: 56137
      aa1e21dc
    • Daniel Dunbar's avatar
      Iterate on sema for :? in Objective-C: · 484603be
      Daniel Dunbar authored
       - Follow C99 behavior of using other operand type when one of
         operands is a null pointer constant.
       - Fix overenthusiastic devolving of any Objective-C types to id:
         o If either operand has an Objective-C object type then:
           - If both operands are interfaces and either operand can be
             assigned to the other, use that type as the composite type.
           - Otherwise, if either type is id, use id as the composite type.
           - Otherwise, warn about incompatible types and use id as the
             composite type.
       - Return handling of qualified idea to separate test following
         general pointer type checking.
         o Upgraded from old code to allow devolving to id (without warning,
           which matches GCC).
       - <rdar://problem/6212771>
      
      Add test case for issues fixed above, XFAIL though because it exposed
      a new issue in property handling.
      
      llvm-svn: 56135
      484603be
Loading