Skip to content
  1. Feb 28, 2009
  2. Feb 18, 2009
  3. Feb 15, 2009
  4. Feb 14, 2009
  5. Feb 11, 2009
  6. Feb 05, 2009
    • Sebastian Redl's avatar
      Put the invalid flag of OwningResult into the Action pointer. · 726a0d95
      Sebastian Redl authored
      This shrinks OwningResult by one pointer. Since it is no longer larger than OwningPtr, merge the two.
      This leads to simpler client code and speeds up my benchmark by 2.7%.
      For some reason, this exposes a previously hidden bug, causing a regression in SemaCXX/condition.cpp.
      
      llvm-svn: 63867
      726a0d95
  7. Jan 29, 2009
  8. Jan 27, 2009
  9. Jan 18, 2009
  10. Jan 12, 2009
  11. Jan 09, 2009
  12. Jan 08, 2009
    • Douglas Gregor's avatar
      Unify the code for defining tags in C and C++, so that we always · 82ac25e4
      Douglas Gregor authored
      introduce a Scope for the body of a tag. This reduces the number of
      semantic differences between C and C++ structs and unions, and will
      help with other features (e.g., anonymous unions) in C. Some important
      points:
      
        - Fields are now in the "member" namespace (IDNS_Member), to keep
          them separate from tags and ordinary names in C. See the new test
          in Sema/member-reference.c for an example of why this matters. In
          C++, ordinary and member name lookup will find members in both the
          ordinary and member namespace, so the difference between
          IDNS_Member and IDNS_Ordinary is erased by Sema::LookupDecl (but
          only in C++!). 
        - We always introduce a Scope and push a DeclContext when we're
          defining a tag, in both C and C++. Previously, we had different
          actions and different Scope/CurContext behavior for enums, C
          structs/unions, and C++ structs/unions/classes. Now, it's one pair
          of actions. (Yay!)
      
      There's still some fuzziness in the handling of struct/union/enum
      definitions within other struct/union/enum definitions in C. We'll
      need to do some more cleanup to eliminate some reliance on CurContext
      before we can solve this issue for real. What we want is for something
      like this:
      
        struct X {
          struct T { int x; } t;
        };
      
      to introduce T into translation unit scope (placing it at the
      appropriate point in the IdentifierResolver chain, too), but it should
      still have struct X as its lexical declaration
      context. PushOnScopeChains isn't smart enough to do that yet, though,
      so there's a FIXME test in nested-redef.c
      
      llvm-svn: 61940
      82ac25e4
  13. Dec 21, 2008
  14. Dec 17, 2008
  15. Dec 13, 2008
  16. Dec 11, 2008
  17. Dec 10, 2008
  18. Dec 09, 2008
  19. Dec 08, 2008
  20. Nov 26, 2008
  21. Nov 25, 2008
  22. Nov 20, 2008
  23. Nov 19, 2008
Loading