Skip to content
  1. Aug 11, 2016
    • Teresa Johnson's avatar
      Revert "Resolution-based LTO API." · cbf684e6
      Teresa Johnson authored
      This reverts commit r278330.
      
      I made a change to the save temps output that is causing issues with the
      bots. Didn't realize this because I had older output files sitting on
      disk in my test output directory.
      
      llvm-svn: 278331
      cbf684e6
    • Teresa Johnson's avatar
      Resolution-based LTO API. · f99573b3
      Teresa Johnson authored
      Summary:
      This introduces a resolution-based LTO API. The main advantage of this API over
      existing APIs is that it allows the linker to supply a resolution for each
      symbol in each object, rather than the combined object as a whole. This will
      become increasingly important for use cases such as ThinLTO which require us
      to process symbol resolutions in a more complicated way than just adjusting
      linkage.
      
      Patch by Peter Collingbourne.
      
      Reviewers: rafael, tejohnson, mehdi_amini
      
      Subscribers: lhames, tejohnson, mehdi_amini, llvm-commits
      
      Differential Revision: https://reviews.llvm.org/D20268
      
      Address review comments
      
      llvm-svn: 278330
      f99573b3
  2. Aug 10, 2016
  3. Aug 09, 2016
  4. Aug 05, 2016
  5. Jul 26, 2016
  6. Jul 12, 2016
  7. Jul 09, 2016
  8. May 24, 2016
    • Justin Bogner's avatar
      test: Be consistent with clang's sanitizer lit config · a5690b00
      Justin Bogner authored
      The logic that sets up lit features for sanitizers is largely copied
      between here and clang, except clang's was fixed some time ago to
      handle multiple sanitizers (ie, Asan + Ubsan). This just makes the
      code in LLVM consistent with how it's done in clang to avoid any
      gotchas by users of this.
      
      llvm-svn: 270510
      a5690b00
  9. May 23, 2016
  10. May 02, 2016
    • Pete Cooper's avatar
      Add llvm-pdbdump to the tool substitutions list in lit. NFC. · 228b1e9a
      Pete Cooper authored
      This adds llvm-pdbdump to the list of tools which get printed with
      the full path in verbose mode.  This makes it easier to take the
      whole run line from verbose output and run it again without prepending
      with the builds bin directory.
      
      llvm-svn: 268250
      228b1e9a
  11. Apr 04, 2016
  12. Mar 29, 2016
  13. Mar 08, 2016
  14. Jan 16, 2016
  15. Jan 09, 2016
  16. Jan 06, 2016
    • Nico Weber's avatar
      Make WinCOFFObjectWriter.cpp's timestamp writing not use ENABLE_TIMESTAMPS · 891419ad
      Nico Weber authored
      LLVM_ENABLE_TIMESTAMPS controls if timestamps are embedded into llvm's
      binaries. Turning it off is useful for deterministic builds.
      
      r246905 made it so that the define suddenly also controls if the binaries that
      the llvm binaries _create_ embed timestamps or not – but this shouldn't be a
      configure-time option. r256203/r256204 added a driver option to toggle this on
      and off, so this patch now passes this driver option in LLVM_ENABLE_TIMESTAMPS
      builds so that if LLVM_ENABLE_TIMESTAMPS is set, the build of LLVM is
      deterministic – but the built clang can still write timestamps into other
      executables when requested.
      
      This also allows removing some of the test machinery added in r292012 to work
      around this problem.
      
      See PR24740 for background.
      http://reviews.llvm.org/D15783
      
      llvm-svn: 256958
      891419ad
  17. Dec 27, 2015
  18. Dec 21, 2015
    • NAKAMURA Takumi's avatar
      check-llvm: Tweak the feature "timestamps" for autoconf. · 8c6c95ad
      NAKAMURA Takumi authored
      Note, ENABLE_TIMESTAMPS is either 1 or 0 in Makefile.config.
      
      llvm-svn: 256138
      8c6c95ad
    • David Majnemer's avatar
      [MC, COFF] Unbreak support for COFF timestamps · 18663f87
      David Majnemer authored
      Support for COFF timestamps was unintentionally broken in r246905 when
      it was conditionally available depending on whether or not LLVM was
      configured with LLVM_ENABLE_TIMESTAMPS.  However, Config/config.h was
      never included which essentially broke the feature.  Due to lax testing,
      the breakage was never identified until we observed strange failures
      during incremental links of Chromium.
      
      This issue is resolved by simply including Config/config.h in
      WinCOFFObjectWriter and teaching lit that the MC/COFF/timestamp.s test
      is conditionally supported depending on LLVM_ENABLE_TIMESTAMPS.  With
      this in place, we can strengthen the test to ensure that it will not
      accidentally get broken in the future.
      
      This fixes PR25891.
      
      llvm-svn: 256137
      18663f87
  19. Dec 20, 2015
  20. Dec 01, 2015
  21. Nov 27, 2015
  22. Nov 19, 2015
  23. Nov 17, 2015
  24. Oct 10, 2015
  25. Oct 09, 2015
  26. Sep 22, 2015
  27. Sep 16, 2015
    • Mehdi Amini's avatar
      Make the default triple optional by allowing an empty string · d178f4fc
      Mehdi Amini authored
      When building LLVM as a (potentially dynamic) library that can be linked against
      by multiple compilers, the default triple is not really meaningful.
      We allow to explicitely set it to an empty string when configuring LLVM.
      In this case, said "target independent" tests in the test suite that are using
      the default triple are disabled by matching the newly available feature
      "default_triple".
      
      Reviewers: probinson, echristo
      Differential Revision: http://reviews.llvm.org/D12660
      
      From: Mehdi Amini <mehdi.amini@apple.com>
      llvm-svn: 247775
      d178f4fc
  28. Sep 02, 2015
    • Justin Bogner's avatar
      test: Only warn about missing substitutions for required tools · 04430aea
      Justin Bogner authored
      Every time lit is invoked, I get warnings like so:
      
        lit.py: lit.cfg:286: note: Did not find llvm-go in /Users/bogner/build/llvm/./bin
        lit.py: lit.cfg:286: note: Did not find Kaleidoscope-Ch3 in /Users/bogner/build/llvm/./bin
      
      Since these tools are only built in certain configs, these warnings
      are superfluous. Change it so that we only warn about tools that are
      built in all configs.
      
      llvm-svn: 246684
      04430aea
  29. Aug 31, 2015
  30. Aug 29, 2015
  31. Aug 27, 2015
Loading