Skip to content
Snippets Groups Projects
  1. Jun 15, 2016
  2. Jun 09, 2016
  3. Jun 04, 2016
  4. Jun 01, 2016
  5. May 31, 2016
  6. May 26, 2016
  7. May 24, 2016
  8. May 09, 2016
  9. May 03, 2016
  10. Apr 27, 2016
  11. Apr 15, 2016
  12. Apr 13, 2016
    • Nemanja Ivanovic's avatar
      Enable support for __float128 in Clang · b2ea6d9a
      Nemanja Ivanovic authored
      This patch corresponds to review:
      http://reviews.llvm.org/D15120
      
      It adds support for the __float128 keyword, literals and a target feature to
      enable it. This support is disabled by default on all targets and any target
      that has support for this type is free to add it.
      
      Based on feedback that I've received from target maintainers, this appears to
      be the right thing for most targets. I have not heard from the maintainers of
      X86 which I believe supports this type. I will subsequently investigate the
      impact of enabling this on X86.
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@266186 91177308-0d34-0410-b5e6-96231b3b80d8
      b2ea6d9a
  13. Mar 24, 2016
  14. Mar 16, 2016
  15. Mar 08, 2016
  16. Mar 03, 2016
  17. Mar 01, 2016
    • Manuel Klimek's avatar
      Optionally demote fatal errors to non-fatal errors. · ac0a11ae
      Manuel Klimek authored
      This behavior is enabled when the new CXTranslationUnit_KeepGoing
      option is passed to clang_parseTranslationUnit{,2}. It is geared
      towards use by IDEs and similar consumers of the clang-c API where
      fatal errors may arise when parsing incomplete code mid-edit, or
      when include paths are not properly configured yet. In such situations
      one still wants to get as much information as possible about a TU.
      Previously, the semantic analysis would not instantiate templates
      or report additional fatal errors after the first fatal error was
      encountered.
      
      Fixes PR24268.
      
      Patch by Milian Wolff.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@262318 91177308-0d34-0410-b5e6-96231b3b80d8
      ac0a11ae
  18. Feb 07, 2016
  19. Feb 03, 2016
  20. Jan 26, 2016
  21. Jan 19, 2016
  22. Jan 16, 2016
  23. Dec 15, 2015
    • Benjamin Kramer's avatar
      [libclang] Add a flag to create the precompiled preamble on the first parse. · bdb67374
      Benjamin Kramer authored
      Summary:
      The current default is to create the preamble on the first reparse, aka
      second parse. This is useful for clients that do not want to block when
      opening a file because serializing the preamble takes a bit of time.
      However, this makes the reparse much more expensive and that may be on the
      critical path as it's the first interaction a user has with the source code.
      
      YouCompleteMe currently optimizes for the first code interaction by parsing
      the file twice when loaded. That's just unnecessarily slow and this flag
      helps to avoid that.
      
      Reviewers: doug.gregor, klimek
      
      Subscribers: cfe-commits
      
      Differential Revision: http://reviews.llvm.org/D15490
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@255635 91177308-0d34-0410-b5e6-96231b3b80d8
      bdb67374
  24. Dec 14, 2015
  25. Dec 10, 2015
  26. Dec 09, 2015
  27. Dec 08, 2015
  28. Dec 03, 2015
  29. Dec 01, 2015
  30. Nov 23, 2015
  31. Nov 18, 2015
Loading