Skip to content
  1. May 18, 2016
  2. May 17, 2016
  3. May 16, 2016
    • Vedant Kumar's avatar
      Revert "Retry^2 "[ProfileData] (llvm) Use Error in InstrProf and Coverage, NFC"" · 85c973d3
      Vedant Kumar authored
      This reverts commit r269694. MSVC says:
      
      error C2086: 'char llvm::ProfErrorInfoBase<enum llvm::instrprof_error>::ID' : redefinition
      
      llvm-svn: 269700
      85c973d3
    • Vedant Kumar's avatar
      Retry^2 "[ProfileData] (llvm) Use Error in InstrProf and Coverage, NFC" · 7cb2fd59
      Vedant Kumar authored
      Transition InstrProf and Coverage over to the stricter Error/Expected
      interface.
      
      Changes since the initial commit:
      - Address undefined-var-template warning.
      - Fix error message printing in llvm-profdata.
      - Check errors in loadTestingFormat() + annotateAllFunctions().
      - Defer error handling in InstrProfIterator to InstrProfReader.
      
      Differential Revision: http://reviews.llvm.org/D19901
      
      llvm-svn: 269694
      7cb2fd59
    • David Blaikie's avatar
      llvm-dwp: Streamline duplicate DWO ID diagnostic handling · d1f7ab33
      David Blaikie authored
      Actually use the error return path rather than printing the duplicate
      information then a separate error. But also just tidy up/deduplicate
      some of the code for generating the diagnostic text.
      
      llvm-svn: 269692
      d1f7ab33
    • Renato Golin's avatar
      [llc] New diagnostic handler · 4b9c0d4d
      Renato Golin authored
      Without a diagnostic handler installed, llc's behaviour is to exit on the first
      error that it encounters. This is very different from the behaviour of clang
      and other front ends, which try to gather as many errors as possible before
      exiting.
      
      This commit adds a diagnostic handler to llc, allowing it to find and report
      more than one error. The old behaviour is preserved under a flag (-exit-on-error).
      
      Some of the tests fail with the new diagnostic handler, so they have to use the
      new flag in order to run under the previous behaviour. Some of these are known
      bugs, others need further investigation. Ideally, we should fix the tests and
      remove the flag at some point in the future.
      
      Reapplied after fixing the LLDB build that was broken due to the new
      DiagnosticSeverity in LLVMContext.h, and fixed an UB in the new change.
      
      Patch by Diana Picus.
      
      llvm-svn: 269655
      4b9c0d4d
    • NAKAMURA Takumi's avatar
      macho2yaml.cpp: Fix "reserved" uninitialized. · 68570b20
      NAKAMURA Takumi authored
      FIXME: It should reflect actual field.
      llvm-svn: 269645
      68570b20
  4. May 15, 2016
  5. May 14, 2016
    • Renato Golin's avatar
      Revert "[llc] New diagnostic handler" · f4917d35
      Renato Golin authored
      This reverts commit r269563. Even though now it passes all LLDB bots
      after a local fix, there's a new buildbot it fails with tests that we
      hadn't seen locally:
      
      http://lab.llvm.org:8011/builders/clang-x86_64-linux-selfhost-modules/builds/15647
      
      Adding those tests to the list to investigate.
      
      llvm-svn: 269568
      f4917d35
    • Renato Golin's avatar
      [llc] New diagnostic handler · c001e67b
      Renato Golin authored
      Without a diagnostic handler installed, llc's behaviour is to exit on the first
      error that it encounters. This is very different from the behaviour of clang
      and other front ends, which try to gather as many errors as possible before
      exiting.
      
      This commit adds a diagnostic handler to llc, allowing it to find and report
      more than one error. The old behaviour is preserved under a flag (-exit-on-error).
      
      Some of the tests fail with the new diagnostic handler, so they have to use the
      new flag in order to run under the previous behaviour. Some of these are known
      bugs, others need further investigation. Ideally, we should fix the tests and
      remove the flag at some point in the future.
      
      Reapplied after fixing the LLDB build that was broken due to the new
      DiagnosticSeverity in LLVMContext.h.
      
      Patch by Diana Picus.
      
      llvm-svn: 269563
      c001e67b
    • Chandler Carruth's avatar
      Revert "Retry "[ProfileData] (llvm) Use Error in InstrProf and Coverage, NFC"" · 59573759
      Chandler Carruth authored
      This reverts commit r269491. It triggers warnings with Clang, breaking
      builds for -Werror users including several build bots.
      
      llvm-svn: 269547
      59573759
    • Mehdi Amini's avatar
      Add testing in llvm-lto for ThinLTO caching. · ab4a8b6c
      Mehdi Amini authored
      Trying to improve code coverage for `make check`
      
      From: mehdi_amini <mehdi_amini@91177308-0d34-0410-b5e6-96231b3b80d8>
      llvm-svn: 269545
      ab4a8b6c
    • Mehdi Amini's avatar
      Revert "Add testing in llvm-lto for ThinLTO caching." · 34b0241b
      Mehdi Amini authored
      This reverts commit r269538 and r269542.
      "rename()" is expected to fail across filesystems, will handle this.
      
      From: Mehdi Amini <mehdi.amini@apple.com>
      llvm-svn: 269543
      34b0241b
    • Mehdi Amini's avatar
      Add testing in llvm-lto for ThinLTO caching. · dec0e54d
      Mehdi Amini authored
      Trying to improve code coverage for `make check`
      
      From: Mehdi Amini <mehdi.amini@apple.com>
      llvm-svn: 269538
      dec0e54d
    • Reid Kleckner's avatar
      [codeview] Add type stream merging prototype · 0b269748
      Reid Kleckner authored
      Summary:
      This code is intended to be used as part of LLD's PDB writing. Until
      that exists, this is exposed via llvm-readobj for testing purposes.
      
      Type stream merging uses the following algorithm:
      
      - Begin with a new empty stream, and a new empty hash table that maps
        from type record contents to new type index.
      - For each new type stream, maintain a map from source type index to
        destination type index.
      - For each record, copy it and rewrite its type indices to be valid in
        the destination type stream.
      - If the new type record is not already present in the destination
        stream hash table, append it to the destination type stream, assign it
        the next type index, and update the two hash tables.
      - If the type record already exists in the destination stream, discard
        it and update the type index map to forward the source type index to
        the existing destination type index.
      
      Reviewers: zturner, ruiu
      
      Subscribers: llvm-commits
      
      Differential Revision: http://reviews.llvm.org/D20122
      
      llvm-svn: 269521
      0b269748
  6. May 13, 2016
Loading