Skip to content
  1. Feb 23, 2012
  2. Feb 22, 2012
    • Chad Rosier's avatar
      Remove extra semi-colons. · 5dfe6dab
      Chad Rosier authored
      llvm-svn: 151169
      5dfe6dab
    • Chandler Carruth's avatar
      Support was removed from LLVM's MIPS backend for the PSP variant of that · 0c7a7cc7
      Chandler Carruth authored
      chip in r139383, and the PSP components of the triple are really
      annoying to parse. Let's leave this chapter behind. There is no reason
      to expect LLVM to see a PSP-related triple these days, and so no
      reasonable motivation to support them.
      
      It might be reasonable to prune a few of the older MIPS triple forms in
      general, but as those at least cause no burden on parsing (they aren't
      both a chip and an OS!), I'm happy to leave them in for now.
      
      llvm-svn: 151156
      0c7a7cc7
  3. Feb 21, 2012
  4. Feb 20, 2012
  5. Feb 19, 2012
  6. Feb 18, 2012
  7. Feb 15, 2012
  8. Feb 12, 2012
  9. Feb 09, 2012
    • David Blaikie's avatar
      Change default error_code ctor to a 'named ctor' so it's more self-documenting. · 18544b96
      David Blaikie authored
      Unify default construction of error_code uses on this idiom so that users don't
      feel compelled to make static globals for naming convenience. (unfortunately I
      couldn't make the original ctor private as some APIs don't return their result,
      instead using an out parameter (that makes sense to default construct) - which
      is a bit of a pity. I did, however, find/fix some cases of unnecessary default
      construction of error_code before I hit the unfixable cases)
      
      llvm-svn: 150197
      18544b96
    • David Blaikie's avatar
      Remove static initializer from DataStream.cpp · e7d7a5df
      David Blaikie authored
      If someone would prefer a clear name for the 'success' error_value we could
      come up with one - potentially just a 'named constructor' style
      'error_value::success()' to make this expression more self-documenting. If
      I see this come up in other cases I'll certainly consider it.
      
      One step along the way to resolving PR11944.
      
      llvm-svn: 150120
      e7d7a5df
  10. Feb 08, 2012
  11. Feb 07, 2012
  12. Feb 06, 2012
  13. Feb 05, 2012
  14. Feb 04, 2012
  15. Jan 31, 2012
  16. Jan 29, 2012
  17. Jan 28, 2012
  18. Jan 25, 2012
  19. Jan 23, 2012
  20. Jan 20, 2012
  21. Jan 19, 2012
  22. Jan 17, 2012
Loading