[lldb] Adjust SourceFileCompleter to use StringRef (#206603)
Instead of storing `const char *` (which are currently backed by
ConstStrings), it should instead store the FileSpec and extract the
Filename and Directory as needed.
[lldb][NFC] Change how Target stores BreakpointNames (#205419)
This changes 2 things:
1) BreakpointNameList is now called BreakpointNameMap to reflect the
actual underlying data structure.
2) BreakpointNameMap goes from a `std::map` to a `llvm::StringMap` to
eliminate the use of ConstString.
[SLP] Apply reused-scalar reduction counters at the vectorized lane
The horizontal reduction reuse-counter scale was placed by deduplicated
candidate order, but the emitted reduction vector lane order is defined by
the root node, which may be reordered or split (SplitVectorize). As a
result a repeat count could be applied to the wrong lane, producing a wrong
reduction result. Place each counter at the lane the matching candidate is
vectorized to.
Fixes #206476
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/206611
[AMDGPU] Autogen checks for tests in AMDGPU Cost Model. NFC (#206595)
Even though there are comments in the test files saying checks
are autogenerated, it seems some checks are not actually updated.
This work autogenerates checks based on the latest llvm source.
RAIDZ: Fix parity regeneration/check condition
Profiling RAIDZ1/dRAID1 resilver I've noticed that they calculate
the parity twice for most of blocks: first to reconstruct the data
column and then to "verify" the parity column. Same time it is
obvious that parity generated from data reconstructed from the
parity will be identical to the original. The code even had this
condition, but it was overridden by ZIO_FLAG_RESILVER check.
I think the ZIO_FLAG_RESILVER condition is not right. Instead we
should check for parity_errors > 0, when we failed to read some
parity columns that we'll need to rewrite. It should not matter
if we are resilvering or just doing self healing on regular read.
Profiling shows this saving ~16% of ZFS CPU time when resilvering
RAIDZ1. RAIDZ2+ are out of luck, unless two disks are replaced
same time, since there is still a parity to verify.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Alexander Motin <alexander.motin at TrueNAS.com>
Closes #18707
[llvm][clang] Remove `format_object_base` forward declarations (#206526)
PR https://github.com/llvm/llvm-project/pull/206319 removed the
`format_object_base` class itself, but not some of its
forward-declarations. NFCI
[clang][docs]Refactor compiler standard references from c94 to C95 (#206403)
The patch changes references to a non existent c94 standard from
to C95 (C90 + AMD1)
Closes #206389
