Skip to content
Snippets Groups Projects
  1. Nov 12, 2014
  2. Feb 25, 2014
  3. Oct 15, 2013
  4. Aug 05, 2013
    • Richard Smith's avatar
      Implement C++'s restrictions on the type of an expression passed to a vararg · 0e218979
      Richard Smith authored
      function: it can't be 'void' and it can't be an initializer list. We give a
      hard error for these rather than treating them as undefined behavior (we can
      and probably should do the same for non-POD types in C++11, but as of this
      change we don't).
      
      Slightly rework the checking of variadic arguments in a function with a format
      attribute to ensure that certain kinds of format string problem (non-literal
      string, too many/too few arguments, ...) don't suppress this error.
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@187735 91177308-0d34-0410-b5e6-96231b3b80d8
      0e218979
  5. Apr 10, 2013
  6. Dec 05, 2012
    • Jordan Rose's avatar
      Format strings: offer a cast to 'unichar' for %C in Objective-C contexts. · 2cd34403
      Jordan Rose authored
      For most cases where a conversion specifier doesn't match an argument,
      we usually guess that the conversion specifier is wrong. However, if
      the argument is an integer type and the specifier is %C, it's likely
      the user really did mean to print the integer as a character.
      
      (This is more common than %c because there is no way to specify a unichar
      literal -- you have to write an integer literal, such as '0x2603',
      and then cast it to unichar.)
      
      This does not change the behavior of %S, since there are fewer cases
      where printing a literal Unicode *string* is necessary, but this could
      easily be changed in the future.
      
      <rdar://problem/11982013>
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@169400 91177308-0d34-0410-b5e6-96231b3b80d8
      2cd34403
  7. Aug 08, 2012
  8. Jul 19, 2012
  9. Jun 05, 2012
    • Jordan Rose's avatar
      Teach format string checking about compile-time CFString constants. · 50687314
      Jordan Rose authored
      Within the guts of CheckFormatHandler, the IsObjCLiteral flag was being used in
      two ways: to see if null bytes were allowed, and to see if the '%@' specifier
      is allowed.* The former usage has been changed to an explicit test and the
      latter pushed down to CheckPrintfHandler and renamed ObjCContext, since it
      applies to CFStrings as well.
      
      * This also changes how wide chars are interpreted; in OS X Foundation, the
      wide character type is 'unichar', a typedef for short, rather than wchar_t.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@157968 91177308-0d34-0410-b5e6-96231b3b80d8
      50687314
  10. May 04, 2012
  11. Apr 06, 2012
  12. Mar 15, 2012
  13. Feb 21, 2012
  14. Feb 06, 2012
  15. Feb 04, 2012
  16. Feb 03, 2012
  17. Jan 31, 2012
  18. Jan 30, 2012
  19. Jan 25, 2012
  20. Jan 20, 2012
  21. Jan 17, 2012
  22. Jun 29, 2011
  23. Jun 15, 2011
  24. Jun 16, 2010
  25. Feb 27, 2010
  26. Jan 30, 2010
  27. Jan 29, 2010
  28. Dec 15, 2009
  29. Dec 14, 2009
  30. Mar 24, 2009
  31. Sep 26, 2008
  32. Jul 26, 2008
  33. Jun 16, 2008
Loading