1. Oct 29, 2021
    • Nicolai Hähnle's avatar
      MachineDominators: Define MachineDomTree type alias · b437aaa6
      Nicolai Hähnle authored
      This is a (very) small move towards making the machine dominators more
      aligned with the IR dominators:
      
      * DominatorTree / MachineDomTree is the class holding the dominator tree
      * DominatorTreeWrapperPass / MachineDominatorTree is the corresponding
        (machine) function pass
      
      This alignment will be used by analyses that are designed as templates
      that work with LLVM IR as well as Machine IR.
      
      Reviewed By: critson
      
      Differential Revision: https://reviews.llvm.org/D112690
      b437aaa6
    • Victor Huang's avatar
      [PowerPC][NFC] Update builtins-ppc-xlcompat-trap-64bit-only.ll and... · 40cad47f
      Victor Huang authored
      [PowerPC][NFC] Update builtins-ppc-xlcompat-trap-64bit-only.ll and builtins-ppc-xlcompat-trap.ll to show full reg names
      40cad47f
    • Fangrui Song's avatar
      [ELF] Change common diagnostics to report both object file location and source file location · 2b1e3241
      Fangrui Song authored
      Many diagnostics use `getErrorPlace` or `getErrorLocation` to report a location.
      In the presence of line table debug information, `getErrorPlace` uses a source
      file location and ignores the object file location. However, the object file
      location is sometimes more useful.
      
      This patch changes "undefined symbol" and "out of range" diagnostics to report
      both object/source file locations. Other diagnostics can use similar format if
      needed.
      
      The key idea is to let `InputSectionBase::getLocation` report the object file
      location and use `getSrcMsg` for source file/line information. `getSrcMsg`
      doesn't leverage `STT_FILE` information yet, but I think the temporary lack of
      the functionality is ok.
      
      For the ARM "branch and link relocation" diagnostic, I arbitrarily place the
      source file location at the end of the line. The diagnostic is not very common
      so its formatting doesn't need to be pretty.
      
      Differential Revision: https://reviews.llvm.org/D112518
      2b1e3241
    • Kazu Hirata's avatar
      [IR] Fix a warning · a88867a0
      Kazu Hirata authored
      This patch fixes:
      
        mlir/lib/IR/BuiltinAttributes.cpp:876:39: error: unused function
        'isComplexOfIntType' [-Werror,-Wunused-function]
      
      in a release build.
      a88867a0
    • Philip Reames's avatar
      6caff716
    • David CARLIER's avatar
      [compiler-rt] update detect_write_exec option for apple devices. · bb168f32
      David CARLIER authored
      Reviewed By: yln, vitalybuka
      
      Differential Revision: https://reviews.llvm.org/D111390
      bb168f32
    • Philip Reames's avatar
      Autogen a test for ease of update · 9ed528e0
      Philip Reames authored
      9ed528e0
    • Chandler Carruth's avatar
      Add support for Bazel builds on Windows with `clang-cl`. · 112dc160
      Chandler Carruth authored
      Adds basic `--config=clang-cl` to set up the basic options needed, and
      then fix a number of issues that surface in Windows builds for me.
      
      With these fixes, `//llvm/...` builds cleanly. One unittest still fails,
      but its just due to running out of stack space due to creating a large
      number of short-lived stack variables. The test should probably be
      decomposed into a set of tests (`LegalizerInfoTest::RuleSets`), but that
      seemed like too invasive of a change here and with everything building
      cleanly this isn't disrupting me experimenting with Windows builds.
      
      Some parts of `//clang/...` builds, but that will require more work.
      112dc160
    • Aart Bik's avatar
      [mlir][sparse] move conversion test back to original CHECK testing · 947e14be
      Aart Bik authored
      Rationale:
      The silent exit(1) gives little clues on where the error occurs on failure
      and may even be confusing at first. The CHECK testing of all computed values
      and indices may be a little bit more elaborate, but it directly pinpoints
      where errors happen if they occur. This style is also consistent with
      the other tests, which I actually prefer.
      
      Reviewed By: bixia
      
      Differential Revision: https://reviews.llvm.org/D112688
      947e14be
  2. Oct 28, 2021