1. [NFC] Rename registerAliasAnalyses -> registerDefaultAliasAnalyses (details)
  2. [clang][cli] Specify correct integer width for -fbuild-session-timestamp (details)
  3. [WebAssembly] Prototype prefetch instructions (details)
  4. [Coverage] Fix test failures from commit rG9f2967bcfe2f (details)
  5. [RISCV] Move shift ComplexPatterns and custom isel to PatFrags with predicates (details)
Commit 28a326eba0a9c367ab6a2d23ca0ae4fb8ab2b536 by aeubanks
[NFC] Rename registerAliasAnalyses -> registerDefaultAliasAnalyses

To clarify that this only affects the "default" AA.

Reviewed By: ychen

Differential Revision:
The file was modifiedllvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp
The file was modifiedllvm/lib/Target/AMDGPU/AMDGPUTargetMachine.h
The file was modifiedllvm/lib/Passes/PassBuilder.cpp
The file was modifiedllvm/include/llvm/Target/TargetMachine.h
The file was modifiedllvm/include/llvm/Passes/PassBuilder.h
Commit f111cf992df4ec00acfdd026eac12b36c3831999 by jan_svoboda
[clang][cli] Specify correct integer width for -fbuild-session-timestamp

This fixes an issue where large integer values were rejected as invalid.

Reviewed By: arphaman

Differential Revision:
The file was modifiedclang/include/clang/Driver/
The file was modifiedclang/unittests/Frontend/CompilerInvocationTest.cpp
Commit 497026c90233e82ffd3ce2438c5f9567be6dabe7 by tlively
[WebAssembly] Prototype prefetch instructions

As proposed in and using the
opcodes used in the V8 prototype: These instructions
are only usable via intrinsics and clang builtins to make them opt-in while they
are being benchmarked.

Differential Revision:
The file was modifiedclang/include/clang/Basic/BuiltinsWebAssembly.def
The file was modifiedclang/test/CodeGen/builtins-wasm.c
The file was modifiedllvm/test/MC/WebAssembly/simd-encodings.s
The file was modifiedllvm/lib/Target/WebAssembly/MCTargetDesc/WebAssemblyMCTargetDesc.h
The file was modifiedclang/lib/CodeGen/CGBuiltin.cpp
The file was addedllvm/test/CodeGen/WebAssembly/simd-prefetch-offset.ll
The file was modifiedllvm/lib/Target/WebAssembly/
The file was modifiedllvm/lib/Target/WebAssembly/AsmParser/WebAssemblyAsmParser.cpp
The file was modifiedllvm/include/llvm/IR/
The file was modifiedllvm/lib/Target/WebAssembly/WebAssemblyISelLowering.cpp
Commit 16f3401eae4310c95163269c41d9b45261f0c7c3 by a-phipps
[Coverage] Fix test failures from commit rG9f2967bcfe2f

Fix test failures with Branch Coverage tests from commit rG9f2967bcfe2f
that failed build on builder clang-x64-windows-msvc while building llvm:
The file was modifiedclang/test/Profile/branch-profdup.cpp
The file was modifiedclang/test/CoverageMapping/branch-constfolded.cpp
The file was modifiedclang/test/CoverageMapping/branch-macros.cpp
The file was modifiedclang/test/CoverageMapping/branch-templates.cpp
The file was modifiedclang/test/Profile/branch-logical-mixed.cpp
The file was modifiedclang/test/CoverageMapping/branch-mincounters.cpp
Commit 7b5a0e2f88eedc1123f4027552940bdf1ab6c03e by craig.topper
[RISCV] Move shift ComplexPatterns and custom isel to PatFrags with predicates

ComplexPatterns are kind of weird, they don't call any of the predicates on their operands. And their "complexity" used for tablegen ordering purposes in the matcher table is hand specified.

This started as an attempt to just use sext_inreg + SLOIPat to implement SLOIW just to have one less Select function. The matching for the or+shl is the same as long as you know the immediate is less than 32 for SLOIW. But that didn't work out because using uimm5 with SLOIPat didn't do anything if it was a ComplexPattern.

I realized I could just use a PatFrag with the opcodes I wanted to match and an immediate predicate would then evaluate correctly. This also computes the complexity just like any other pattern does. Then I just needed to check the constraints on the immediates in the predicate. Conveniently the predicate is evaluated after the fragment has been matched. So the structure has already been checked, we just need to find the constants.

I'll note that this is unusual, I didn't find any other targets looking through operands in PatFrag predicate. There is a PredicateCodeUsesOperands feature that can be used to collect the operands into an array that is used by AMDGPU/ I believe that feature exists to handle commuted matching, but since the nodes here use constants, they aren't ever commuted

Differential Revision:
The file was modifiedllvm/lib/Target/RISCV/RISCVISelDAGToDAG.cpp
The file was modifiedllvm/lib/Target/RISCV/
The file was modifiedllvm/lib/Target/RISCV/RISCVISelDAGToDAG.h
The file was modifiedllvm/lib/Target/RISCV/