[DAG] isIdentityElement - use KnownBits instead of constant splat to match identity constants (#197455)
This works better with the DemandedElts mask to match hidden identity
constants (zero in particular.....).
I need this for the ongoing work to improve VECREDUCE simplification to
match identity elements (legalisation pads with identity elements) in an
expanded reduction shuffle chain.
[LoopInterchange] Handle PHI nodes in inner loop preheader (#196691)
Fixes #196242
LoopInterchange crashes when the inner loop preheader contains a
single-incoming PHI node.
This fix folds single-incoming PHI nodes by replacing them with their
incoming value and then erasing the PHI nodes.
Added a regression test under llvm/test/Transforms/LoopInterchange/
using the reproducer from issue #196242.
[LV] Implement usesFirstLaneOnly for VPWidenCallRecipe (#196562)
In order to avoid potentially introducing broadcasts for uniform or
linear arguments for widened calls, implement usesFirstLaneOnly for
VPWidenCallRecipe. Will hopefully make the cost model slightly more
accurate.
Removed instcombine pass from the uniform args tests, since removing
the broadcasts was the main reason for it being called.
Should help out #195444
[FileCheck][NFC] Introduce Mid/Tail to -dump-input MarkerStyle (#196799)
Normally, Head is something like `^` and Mid and Tail are just `~`.
However, the upcoming search range markers will have Head as `{`, Mid as
` `, and Tail as `}`. This patch separately introduces the Mid/Tail
support to facilitate the review, but it is not used for anything yet
here.
This PR is stacked on PR #196797.
[FileCheck][NFC] Introduce InputAnnotationLabeler for -dump-input (#196797)
This patch adds `InputAnnotationLabeler` to make `buildInputAnnotations`
a little easier to understand, and a future patch will reuse it
elsewhere. This patch also cleans up some related symbol names and
comments for better consistency and clarity.
lib/libc/README: Note that jemalloc definition has moved.
Should maybe find a better example than malloc/free for this but
let's at least fix this one point of confusion.
[ExtractAPI] Add support for anyAppleOS (#197929)
6c8940ccad31457aadb48c6f2bce139b1c5dda01 introduced support for
anyAppleOS, which can be used to indicate availability for all Apple
platforms in a single availability attribute.
3089120f0cd2fe78911d1bc9703764a07fa7eb32 updated it to preserve the
original attribute info and store the inferred platform-specific
attribute in a separate field which, if present, is returned by
`getEffectiveAttr()`.
With these changes, ExtractAPI now reports these availabilities verbatim
for an "anyAppleOS" platform as the availability info for Decls directly
uses the availability attribute without fetching the effective
attribute. The expected output would be the target platform for which
the symbol graph is being built. This patch updates the availability
collection logic to use `getEffectiveAttr()` and include the target
platform instead of "anyAppleOS" for symbol availabilities in symbol
graphs.
rdar://174558184
devel/cargo-nextest: update to 0.9.135
0.9.135
- Fixed an issue with a from-crates.io build.
0.9.134
Added
- Nextest now provides a JSON Schema for repository configuration at .config/nextest.toml, enabling validation and IDE autocompletion via the Tombi language server.
Thanks ya7010 for your first contribution, and for maintaining Tombi!
(Note that the Taplo language server is not supported due to a crash bug. The schema has been tested to work with Tombi.)
- For target triples that nextest doesn't have built-in information about, nextest now invokes rustc --print=cfg --target=<triple> to resolve platform information before falling back to heuristic detection. This is particularly useful for custom builds of the Rust toolchain. (#3331)
Thanks mhatzl for your first contribution!
Changed
[7 lines not shown]
