Skip to content
  1. Jul 17, 2012
  2. Jul 16, 2012
  3. Jul 15, 2012
  4. Jul 13, 2012
  5. Jul 12, 2012
  6. Jul 11, 2012
    • Dmitri Gribenko's avatar
      Enable comment parsing and semantic analysis to emit diagnostics. A few · f26054f0
      Dmitri Gribenko authored
      diagnostics implemented -- see testcases.
      
      I created a new TableGen file for comment diagnostics,
      DiagnosticCommentKinds.td, because comment diagnostics don't logically
      fit into AST diagnostics file.  But I don't feel strongly about it.
      
      This also implements support for self-closing HTML tags in comment
      lexer and parser (for example, <br />).
      
      In order to issue precise diagnostics CommentSema needs to know the
      declaration the comment is attached to.  There is no easy way to find a decl by 
      comment, so we match comments and decls in lockstep: after parsing one
      declgroup we check if we have any new, not yet attached comments.  If we do --
      then we do the usual comment-finding process.
      
      It is interesting that this automatically handles trailing comments.
      We pick up not only comments that precede the declaration, but also
      comments that *follow* the declaration -- thanks to the lookahead in
      the lexer: after parsing the declgroup we've consumed the semicolon
      and looked ahead through comments.
      
      Added -Wdocumentation-html flag for semantic HTML errors to allow the user to 
      disable only HTML warnings (but not HTML parse errors, which we emit as
      warnings in -Wdocumentation).
      
      llvm-svn: 160078
      f26054f0
    • Rafael Espindola's avatar
      Handle #pragma visibility in explicit specializations and enums. · 1fa9fade
      Rafael Espindola authored
      llvm-svn: 160057
      1fa9fade
    • Rafael Espindola's avatar
      Don't process #pragma visibility during instantiation. The visibility of the · 5f0a1b89
      Rafael Espindola authored
      instantiation depends on the template, its arguments and parameters, but not
      where it is instantiated.
      
      llvm-svn: 160034
      5f0a1b89
  7. Jul 10, 2012
  8. Jul 09, 2012
    • Abramo Bagnara's avatar
      The delete argument should not be converted to void*. · cb435673
      Abramo Bagnara authored
      llvm-svn: 159961
      cb435673
    • Jordan Rose's avatar
      Downgrade the "direct comparison" error for ObjC literals to a warning. · f9198030
      Jordan Rose authored
      Chris pointed out that while the comparison is certainly problematic
      and does not have well-defined behavior, it isn't any worse than some
      of the other abuses that we merely warn about and doesn't need to make
      the compilation fail.
      
      Revert the release notes change (r159766) now that this is just a new warning.
      
      llvm-svn: 159939
      f9198030
    • Alexander Kornienko's avatar
      Inline storage of attributes in AttributedStmt. · 20f6fc62
      Alexander Kornienko authored
      llvm-svn: 159925
      20f6fc62
    • Richard Smith's avatar
      PR13136: · 34349003
      Richard Smith authored
       * When substituting a reference to a non-type template parameter pack where the
         corresponding argument is a pack expansion, transform into an expression
         which contains an unexpanded parameter pack rather than into an expression
         which contains a pack expansion. This causes the SubstNonTypeTemplateParmExpr
         to be inside the PackExpansionExpr, rather than outside, so the expression
         still looks like a pack expansion and can be deduced.
      
       * Teach MarkUsedTemplateParameters that we can deduce a reference to a template
         parameter if it's wrapped in a SubstNonTypeTemplateParmExpr (such nodes are
         added during alias template substitution).
      
      llvm-svn: 159922
      34349003
  9. Jul 08, 2012
  10. Jul 07, 2012
  11. Jul 06, 2012
  12. Jul 05, 2012
    • Richard Smith's avatar
      PR13273: When performing list-initialization with an empty initializer list, · d86812d9
      Richard Smith authored
      actually perform value initialization rather than trying to fake it with a call
      to the default constructor. Fixes various bugs related to the previously-missing
      zero-initialization in this case.
      
      I've also moved this and the other list initialization 'special case' from
      TryConstructorInitialization into TryListInitialization where they belong.
      
      llvm-svn: 159733
      d86812d9
  13. Jul 04, 2012
Loading