Changes

Changes from Git (git https://github.com/llvm/llvm-project.git)

Summary

[COFF] Use range for on relocations, NFC (details)
Revert "[clang] Change builtin object size when subobject is invalid" (details)
Revert "[DAGCombiner] Enable SimplifyDemandedBits vector support for TRUNCATE" (details)
[NPM][Inliner] Factor ImportedFunctionStats in the InlineAdvisor (details)

Commit 69e0bc77a5d74a5f0e57ad3e7a22ce4fba210b85 by rnk [COFF] Use range for on relocations, NFC
	lld/COFF/Chunks.cpp
Commit b270fd59f0a86fe737853abc43e76b9d29a67eea by George Burgess IV Revert "[clang] Change builtin object size when subobject is invalid" This reverts commit 275f30df8ad6de75e1f29e4b33eaeb67686caf0d. As noted on the code review (https://reviews.llvm.org/D92892), this change causes us to reject valid code in a few cases. Reverting so we have more time to figure out what the right fix{es are, is} here.
	clang/test/CodeGen/object-size.c
	clang/lib/AST/ExprConstant.cpp
Commit a51226057fc30510ac86b32a36a9769ddbf4c318 by hans Revert "[DAGCombiner] Enable SimplifyDemandedBits vector support for TRUNCATE" It caused "Vector shift amounts must be in the same as their first arg" asserts in Chromium builds. See the code review for repro instructions. > Add DemandedElts support inside the TRUNCATE analysis. > > Differential Revision: https://reviews.llvm.org/D56387 This reverts commit cad4275d697c601761e0819863f487def73c67f8.
	llvm/test/CodeGen/X86/min-legal-vector-width.ll
	llvm/test/CodeGen/ARM/lowerMUL-newload.ll
	llvm/test/CodeGen/Thumb2/mve-vmulh.ll
	llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp
	llvm/test/CodeGen/AMDGPU/widen-smrd-loads.ll
	llvm/test/CodeGen/AArch64/lowerMUL-newload.ll
	llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp
	llvm/lib/Target/AArch64/AArch64ISelLowering.cpp
	llvm/test/CodeGen/Thumb2/mve-satmul-loops.ll
	llvm/test/CodeGen/AArch64/aarch64-smull.ll
	llvm/test/CodeGen/X86/vector-trunc.ll
	llvm/test/CodeGen/X86/combine-sra.ll
	llvm/test/CodeGen/X86/known-signbits-vector.ll
Commit e8aec763a57e211420dfceb2a8dc6b88574924f3 by mtrofin [NPM][Inliner] Factor ImportedFunctionStats in the InlineAdvisor When using 2 InlinePass instances in the same CGSCC - one for other mandatory inlinings, the other for the heuristic-driven ones - the order in which the ImportedFunctionStats would be output-ed would depend on the destruction order of the inline passes, which is not deterministic. This patch moves the ImportedFunctionStats responsibility to the InlineAdvisor to address this problem. Differential Revision: https://reviews.llvm.org/D94982
	llvm/include/llvm/Transforms/IPO/Inliner.h
	llvm/test/Transforms/Inline/inline_stats.ll
	llvm/include/llvm/Analysis/MLInlineAdvisor.h
	llvm/lib/Analysis/InlineAdvisor.cpp
	llvm/lib/Transforms/IPO/Inliner.cpp
	llvm/lib/Transforms/Utils/ImportedFunctionsInliningStatistics.cpp
	llvm/include/llvm/Analysis/InlineAdvisor.h
	llvm/include/llvm/Transforms/Utils/ImportedFunctionsInliningStatistics.h
	llvm/lib/Transforms/IPO/SampleProfile.cpp
	llvm/lib/Analysis/ReplayInlineAdvisor.cpp
	llvm/include/llvm/Analysis/ReplayInlineAdvisor.h
	llvm/lib/Analysis/MLInlineAdvisor.cpp