FailedChanges

Summary

  1. [mlir][Linalg] NFC : Move fusion on tensors to separate file. (details)
  2. [runtimes] Remove TOOLCHAIN_TOOLS specialization (details)
  3. [NFC] Let (MC)Register APIs check isStackSlot (details)
  4. [flang] Add checks for misuse of formatted I/O APIs in unformatted I/O statement (details)
Commit c6ea095b9756dff035aed27e7b5b44bf42d22462 by ravishankarm
[mlir][Linalg] NFC : Move fusion on tensors to separate file.

Differential Revision: https://reviews.llvm.org/D88633
The file was addedmlir/lib/Dialect/Linalg/Transforms/FusionOnTensors.cpp
The file was modifiedmlir/lib/Dialect/Linalg/Transforms/CMakeLists.txt
The file was modifiedmlir/lib/Dialect/Linalg/Transforms/Fusion.cpp
Commit dcb5b6dfbfb5dafb66797e8dba2f04eb76a153b7 by smeenai
[runtimes] Remove TOOLCHAIN_TOOLS specialization

https://reviews.llvm.org/D88310 fixed the AIX issue in LLVMExternalProjectUtils,
so we shouldn't need the workaround in the runtimes build anymore. I'm
reverting it because it prevents the target-specific tool selection in
LLVMExternalProjectUtils from taking effect, which we rely on for our
runtimes builds.

Reviewed By: daltenty

Differential Revision: https://reviews.llvm.org/D88627
The file was modifiedllvm/runtimes/CMakeLists.txt
Commit 17640c5aac649c154959ca1075953f0d252a4a5b by mtrofin
[NFC] Let (MC)Register APIs check isStackSlot

The user is expected to make the isStackSlot check before calling isPhysicalRegister
or isVirtualRegister. The APIs assert otherwise. We can improve the usability
of these APIs by carrying out the check in the 2 APIs: they become a
complete "source of truth" and remove an extra responsibility from the
user.

Differential Revision: https://reviews.llvm.org/D88598
The file was modifiedllvm/include/llvm/CodeGen/Register.h
The file was modifiedllvm/include/llvm/MC/MCRegister.h
Commit cdfb95ad580fbf366a9bffc5082df22e9d2b5fa3 by pklausler
[flang] Add checks for misuse of formatted I/O APIs in unformatted I/O statement

Add checking to I/O statement APIs to catch cases where the formatted
I/O data item transfer routines like OutputInteger64 are being
incorrectly used for unformatted I/O, which should use the
unformatted block or descriptor-based data item interfaces.

Differential revision: https://reviews.llvm.org/D88672
The file was modifiedflang/runtime/type-code.cpp
The file was modifiedflang/runtime/io-stmt.h
The file was modifiedflang/runtime/io-api.cpp
The file was modifiedflang/runtime/io-api.h
The file was modifiedflang/runtime/unit.cpp