[Flang] Mark save-mlir-temps.f90 unsupported (#191686)
This was marked as xfail earlier for some .prefalign fixes, but is
unexpectedly passing on AArch64 Premerge CI.
Just mark it unsupported for now to get things back to green.
[Clang-tidy] Add dummy compile_commands.json for broken test (#191635)
Consequence of https://github.com/llvm/llvm-project/issues/182526.
With PCH used for unit tests (#191402), this breaks now due to matching:
llvm-build/tools/clang/tools/extra/test/clang-tidy/infrastructure/Output/custom-query-check.cpp.tmp/cqc-main.cpp
with:
llvm-build/tools/clang/tools/extra/clangd/unittests/DecisionForestRuntimeTest.cpp
[ELF] Move ++nextGroupId from InputFile ctor to callers. NFC (#191685)
Move this side effect to the call sites in addFile() where the groupId
assignment is more visible.
This makes InputFile construction safe to call from parallel contexts.
[RISCV] Split LMUL=8 f16 fixed vector (s/u)ittofp/fpto(s/u)i before promoting. (#191568)
The conversion needs to be done by promoting to f32. If we're already at
LMUL=8, we need to split before we can promote.
[LLDB] Silence warnings when building on Windows (#191566)
Fixes a few warnings found while building the LLVM installer with
`llvm/utils/release/build_llvm_release.bat --x64 --version 23.0.0
--skip-checkout --local-python`.
[clang-doc] Avoid merging into default Info types
When merging into arenas, the code assumed that all using a default
constructed info would be safe, since in the merge we replace any
differing data. However, that appears to be a risky assumption, due
to default initialized members participating in comparisons, and
other operations, leading the program to read garbage data in some
cases. Earlier patches added default initializers to these fields,
but we should prefer (which the old code used to do) to just start
with properly initialized and complete data from the start.
This patch updates the remaining Info types to have copy constructors
that support choosing the arena to allocate into. This is already the
strategy used in several places to avoid use after free bugs. Since
the handling is now uniform, we can simplify things a bit at the same
time and extract the cloning operation into a helper, making the logic
very clear.
This should avoid any potential pitfalls or missed cases that resulted
in the errors discover after landing #190054.