Skip to content
Snippets Groups Projects
  1. Jun 10, 2016
  2. Jun 09, 2016
  3. Jun 06, 2016
  4. May 10, 2016
  5. Apr 28, 2016
  6. Apr 27, 2016
    • Peter Collingbourne's avatar
      Rework interface for bitset-using features to use a notion of LTO visibility. · 47213cf9
      Peter Collingbourne authored
      Bitsets, and the compiler features they rely on (vtable opt, CFI),
      only have visibility within the LTO'd part of the linkage unit. Therefore,
      only enable these features for classes with hidden LTO visibility. This
      notion is based on object file visibility or (on Windows)
      dllimport/dllexport attributes.
      
      We provide the [[clang::lto_visibility_public]] attribute to override the
      compiler's LTO visibility inference in cases where the class is defined
      in the non-LTO'd part of the linkage unit, or where the ABI supports
      calling classes derived from abstract base classes with hidden visibility
      in other linkage units (e.g. COM on Windows).
      
      If the cross-DSO CFI mode is enabled, bitset checks are emitted even for
      classes with public LTO visibility, as that mode uses a separate mechanism
      to cause bitsets to be exported.
      
      This mechanism replaces the whole-program-vtables blacklist, so remove the
      -fwhole-program-vtables-blacklist flag.
      
      Because __declspec(uuid()) now implies [[clang::lto_visibility_public]], the
      support for the special attr:uuid blacklist entry is removed.
      
      Differential Revision: http://reviews.llvm.org/D18635
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@267784 91177308-0d34-0410-b5e6-96231b3b80d8
      47213cf9
  7. Apr 12, 2016
  8. Mar 01, 2016
  9. Feb 26, 2016
  10. Feb 24, 2016
  11. Jan 26, 2016
  12. Dec 16, 2015
  13. Dec 09, 2015
  14. Dec 07, 2015
  15. Dec 03, 2015
  16. Nov 24, 2015
  17. Nov 20, 2015
  18. Nov 11, 2015
  19. Nov 03, 2015
  20. Oct 30, 2015
  21. Oct 20, 2015
    • Chris Bieneman's avatar
      [CMake] Make external compiler-rt install scripts relative to CMAKE_INSTALL_PREFIX. · 5fd2cdb7
      Chris Bieneman authored
      This change makes LLVM_BUILD_EXTERNAL_COMPILER_RT work correctly when overriding CMAKE_INSTALL_PREFIX on the install action (which is how LLVM_CREATE_XCODE_TOOLCHAIN works).
      
      This fix is two parts:
      (1) Pass CMAKE_INSTALL_PREFIX in as a variable from the parent install to the child install
      (2) When passing COMPILER_RT_INSTALL_PATH into the external project make sure it is passed as a string not a path.
      
      Not specifying the full path for COMPILER_RT_INSTALL_PATH isn't enough to fix the issue because relative paths specified on the CMake command line are expanded relative to the working directory before the cache is populated. Forcing this to a string allows it to remain a relative path through to the install() calls. Relative paths specified in install() calls are expanded relative to CMAKE_INSTALL_PREFIX at install time.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@250834 91177308-0d34-0410-b5e6-96231b3b80d8
      5fd2cdb7
  22. Oct 13, 2015
  23. Oct 12, 2015
  24. Oct 04, 2015
  25. Sep 24, 2015
  26. Mar 24, 2015
  27. Feb 18, 2015
  28. Feb 17, 2015
  29. Dec 18, 2014
  30. Nov 10, 2014
  31. Nov 07, 2014
  32. May 22, 2014
  33. May 15, 2014
Loading