Skip to content
Snippets Groups Projects
  1. Jan 03, 2018
  2. Jan 01, 2018
    • Serge Pavlov's avatar
      Fixed markup formatting · 39c04dc5
      Serge Pavlov authored
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321623 91177308-0d34-0410-b5e6-96231b3b80d8
      39c04dc5
    • Serge Pavlov's avatar
      Enable configuration files in clang · 5f7f2c06
      Serge Pavlov authored
      Clang is inherently a cross compiler and can generate code for any target
      enabled during build. It however requires to specify many parameters in the
      invocation, which could be hardcoded during configuration process in the
      case of single-target compiler. The purpose of configuration files is to
      make specifying clang arguments easier.
      
      A configuration file is a collection of driver options, which are inserted
      into command line before other options specified in the clang invocation.
      It groups related options together and allows specifying them in simpler,
      more flexible and less error prone way than just listing the options
      somewhere in build scripts. Configuration file may be thought as a "macro"
      that names an option set and is expanded when the driver is called.
      
      Use of configuration files is described in `UserManual.rst`.
      
      Differential Revision: https://reviews.llvm.org/D24933
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321621 91177308-0d34-0410-b5e6-96231b3b80d8
      5f7f2c06
  3. Dec 30, 2017
    • Serge Pavlov's avatar
      Reverted 321587: Enable configuration files in clang · 509607e4
      Serge Pavlov authored
      Need to check targets in tests more carefully.
      
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321588 91177308-0d34-0410-b5e6-96231b3b80d8
      509607e4
    • Serge Pavlov's avatar
      Enable configuration files in clang · 67245e0d
      Serge Pavlov authored
      Clang is inherently a cross compiler and can generate code for any target
      enabled during build. It however requires to specify many parameters in the
      invocation, which could be hardcoded during configuration process in the
      case of single-target compiler. The purpose of configuration files is to
      make specifying clang arguments easier.
      
      A configuration file is a collection of driver options, which are inserted
      into command line before other options specified in the clang invocation.
      It groups related options together and allows specifying them in simpler,
      more flexible and less error prone way than just listing the options
      somewhere in build scripts. Configuration file may be thought as a "macro"
      that names an option set and is expanded when the driver is called.
      
      Use of configuration files is described in `UserManual.rst`.
      
      Differential Revision: https://reviews.llvm.org/D24933
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321587 91177308-0d34-0410-b5e6-96231b3b80d8
      67245e0d
  4. Dec 29, 2017
  5. Dec 22, 2017
  6. Dec 21, 2017
  7. Dec 18, 2017
  8. Dec 14, 2017
    • Aaron Ballman's avatar
      Harmonize GNU- and C++-style attribute spellings. · 8387eb5f
      Aaron Ballman authored
      Most attributes will now use the Clang<"name"> construct to provide both __attribute__((name)) and [[clang::name]] syntaxes for the attribute. Attributes deviating from this should be marked with a comment explaining why they are not supported under both spellings. Common reasons are: the attribute is provided by some other specification that controls the syntax or the attribute cannot be exposed under a particular spelling for some given reason.
      
      Because this is a mechanical change that only introduces new spellings, there are no test cases for the commit.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@320752 91177308-0d34-0410-b5e6-96231b3b80d8
      8387eb5f
    • Alex Lorenz's avatar
      [Preprocessor] Implement __is_target_{arch|vendor|os|environment} function-like · d0aceebb
      Alex Lorenz authored
      builtin macros
      
      This patch implements the __is_target_arch, __is_target_vendor, __is_target_os,
      and __is_target_environment Clang preprocessor extensions that were proposed by
      @compnerd in Bob's cfe-dev post:
      http://lists.llvm.org/pipermail/cfe-dev/2017-November/056166.html.
      
      These macros can be used to examine the components of the target triple at
      compile time. A has_builtin(is_target_???) preprocessor check can be used to
      check for their availability.
      
      __is_target_arch allows you to check if an arch is specified without worring
      about a specific subarch, e.g.
      
      __is_target_arch(arm) returns 1 for the target arch "armv7"
      __is_target_arch(armv7) returns 1 for the target arch "armv7"
      __is_target_arch(armv6) returns 0 for the target arch "armv7"
      
      __is_target_vendor and __is_target_environment match the specific vendor
      or environment. __is_target_os matches the specific OS, but
      __is_target_os(darwin) will match any Darwin-based OS. "Unknown" can be used
      to test if the triple's component is specified.
      
      rdar://35753116
      
      Differential Revision: https://reviews.llvm.org/D41087
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@320734 91177308-0d34-0410-b5e6-96231b3b80d8
      d0aceebb
  9. Dec 11, 2017
  10. Dec 09, 2017
  11. Dec 08, 2017
  12. Dec 07, 2017
  13. Dec 05, 2017
  14. Dec 04, 2017
  15. Nov 30, 2017
  16. Nov 29, 2017
  17. Nov 27, 2017
  18. Nov 23, 2017
  19. Nov 22, 2017
  20. Nov 21, 2017
  21. Nov 20, 2017
  22. Nov 17, 2017
  23. Nov 14, 2017
  24. Nov 13, 2017
  25. Nov 12, 2017
  26. Nov 11, 2017
  27. Nov 09, 2017
Loading