Changes

Summary

[mlir][python] Aggressively avoid name collisions in generated python ODS code. (details)
[ORC] Move Orc RPC code into Shared, rename some RPC types. (details)
[PowerPC] Remaining KnownBits should be constant when performing non-sign comparison (details)
[PowerPC] Add mir test to show effect of `optimizeCompareInstr` when `equalityOnly` is true. NFC. (details)

Commit 8a1f1a100cce6ed9b52aedbbf03da887833508be by stellaraccident [mlir][python] Aggressively avoid name collisions in generated python ODS code. * When porting npcomp to use these bindings, I ran into enough patterns of collisions that I decided to be somewhat draconian about not polluting the namespace. * With these changes all of the npcomp dialects generate and pass what tests we have. Reviewed By: mehdi_amini Differential Revision: https://reviews.llvm.org/D93920
	mlir/test/mlir-tblgen/op-python-bindings.td
	mlir/tools/mlir-tblgen/OpPythonBindingGen.cpp
	mlir/include/mlir/Bindings/Python/Attributes.td
Commit 5efc71e119d4eba235209d262e7d171361a0b9be by Lang Hames [ORC] Move Orc RPC code into Shared, rename some RPC types. Moves all headers from Orc/RPC to Orc/Shared, and from the llvm::orc::rpc namespace into llvm::orc::shared. Also renames RPCTypeName to SerializationTypeName and Function to RPCFunction. In addition to being a more reasonable home for this code, this will make it easier for the upcoming Orc runtime to re-use the Serialization system for creating and parsing wrapper-function binary blobs.
	llvm/tools/lli/RemoteJITUtils.h
	llvm/unittests/ExecutionEngine/Orc/RPCUtilsTest.cpp
	llvm/tools/lli/lli.cpp
	llvm/tools/llvm-jitlink/llvm-jitlink-executor/llvm-jitlink-executor.cpp
	llvm/include/llvm/ExecutionEngine/Orc/RPC/RPCSerialization.h
	llvm/tools/llvm-jitlink/llvm-jitlink.cpp
	llvm/unittests/ExecutionEngine/Orc/QueueChannel.h
	llvm/include/llvm/ExecutionEngine/Orc/OrcRPCTargetProcessControl.h
	llvm/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetClient.h
	llvm/include/llvm/ExecutionEngine/Orc/Shared/FDRawByteChannel.h
	llvm/include/llvm/ExecutionEngine/Orc/RPC/RPCUtils.h
	llvm/include/llvm/ExecutionEngine/Orc/Shared/RPCUtils.h
	llvm/tools/llvm-jitlink/llvm-jitlink.h
	llvm/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetServer.h
	llvm/tools/lli/ChildTarget/ChildTarget.cpp
	llvm/include/llvm/ExecutionEngine/Orc/Shared/Serialization.h
	llvm/include/llvm/ExecutionEngine/Orc/RPC/RawByteChannel.h
	llvm/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetRPCAPI.h
	llvm/include/llvm/ExecutionEngine/Orc/RPC/FDRawByteChannel.h
	llvm/include/llvm/ExecutionEngine/Orc/Shared/RawByteChannel.h
	llvm/lib/ExecutionEngine/Orc/Shared/RPCError.cpp
	llvm/include/llvm/ExecutionEngine/Orc/TargetProcess/OrcRPCTPCServer.h
Commit f904d50c29f23510cdbae0579085ae7ffebc1f63 by lkail [PowerPC] Remaining KnownBits should be constant when performing non-sign comparison In `PPCTargetLowering::DAGCombineTruncBoolExt`, when checking if it's correct to perform the transformation for non-sign comparison, as the comment says ``` // This is neither a signed nor an unsigned comparison, just make sure // that the high bits are equal. ``` Origin check ``` if (Op1Known.Zero != Op2Known.Zero \|\| Op1Known.One != Op2Known.One) return SDValue(); ``` is not strong enough. For example, ``` Op1Known = 111x000x; Op2Known = 111x000x; ``` Bit 4, besides bit 0, is still unknown and affects the final result. This patch fixes https://bugs.llvm.org/show_bug.cgi?id=48388. Reviewed By: nemanjai, #powerpc Differential Revision: https://reviews.llvm.org/D93092
	llvm/lib/Target/PowerPC/PPCISelLowering.cpp
	llvm/test/CodeGen/PowerPC/pr48388.ll
Commit e3e25cfb44bc2a35e3b53d62d37c27b7d13157b6 by lkail [PowerPC] Add mir test to show effect of `optimizeCompareInstr` when `equalityOnly` is true. NFC.
	llvm/test/CodeGen/PowerPC/peephole-cmp-eq.mir