[Flang] Coarray allocation, update error for pointer component #193829 (#194651)
The TODO message in `verify()` was not completly displayed, so it has
been replaced by `emitErrorOp`.
In addition, the test in `ConvertVariable` has been updated by adding
pointer direct component case.
Fix #193829
(cherry picked from commit 9adc2537177d0813301b3eab1bae906735c984a4)
[lldb] Fix typo in SBUnixSignals.get_unix_signals_list (#213527)
Found when looking through the generated Python file. `sig` doesn't
exist in that context, it should be `idx`.
(cherry picked from commit def770df8325fb60107c24a2de3068aa762754ab)
workflows/release-binaries: Always dump Wix log on Windows (#212056)
Dumping it only on successful builds isn't useful.
(cherry picked from commit cb274010df165e9187233b50babc89fff2103ed5)
oxipng: updated to 10.2.0
10.2.0
[Performance] Improve performance of filtering and reductions.
[Improvement] Balance changes to level presets for better/faster results.
[Improvement] Improve optimization of indexed images.
[Improvement] Slightly improve optimization of interlaced images.
[Improvement] Make --keep more robust, no longer stripping certain chunks regardless.
[Misc] Show oxipng version in verbose output.
[Misc] Bump minimum Rust version to 1.88.0.
[BOLT] Flip the first and last bits of build ID (#214784)
With only the last bit in a build ID flipped, some crash analysis or
symbolication tools that derive module ID from the first 16 bytes are
not able to differentiate pre- and post-BOLT libraries if both are
archived. So besides the last bit, we now also flip the high bit of
the first byte in a build ID.
[flang] Defer typing of forward-referenced DATA implied-DO indices (#214473)
F2023 19.4 p5 gives a data-i-do-variable without an explicit
integer-type-spec the type that its name would have as a variable of the
innermost scoping unit including the DATA statement. That is a property
of the whole scoping unit: since a data-stmt is a declaration-construct,
the type declaration statement establishing the name's type may follow
the DATA statement in the same specification part. Name resolution
resolved the index eagerly at the DATA statement, so under IMPLICIT
NONE(TYPE) a later declaration drew a spurious "No explicit type
declared" error, and without IMPLICIT NONE a later declaration with a
non-default kind was ignored.
Defer the typing of such indices to the end of the specification part,
mirroring the existing deferral for ordinary DATA statement objects.
DATA statements in an execution part keep the current eager resolution.
Assisted-by: AI
p5-Math-Prime-Util-GMP: update to 0.54.
0.54 2026-08-08
[API CHANGES]
- lucas_sequence and is_frobenius_pseudoprime take any integer P,Q
instead of only native.
- multifactorial supports large integer n,m. m must be positive.
- factor accepts negative inputs. In list context, negative inputs have
a leading -1 factor. Scalar context counts factors of the absolute
value and does not count the sign.
- Ranged moebius and euler_phi, plus sieve_primes, sieve_twin_primes,
and sieve_prime_cluster, return the result count in scalar context.
[ADDED]
[91 lines not shown]
[clang-tidy][docs] Rename bugprone check docs to Markdown [3/4] (#214421)
Tracking issue: #201242
See the [migration guide] for more information.
[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines
This is the mechanical rename for part 3/4 of the remaining `bugprone`
check documentation.
The rewrite is provided by the next PR in this stack.
[clang-tidy][docs] Rewrite bugprone check docs to Markdown [3/4] (#214422)
Tracking issue: #201242
See the [migration guide] for more information.
[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines
This rewrites part 3/4 of the remaining bugprone check documentation
from reST to MyST Markdown.
AI Usage: This was prepared with rst2myst and GPT5.6-assisted cleanup.
I manually verified that the documentation renders as expected.
Preview site:
https://broken.life/llvm-staging/bugprone-markdown-port/
[mlir][Transforms] Check successor operand types before merging identical blocks (#215036)
Merging identical blocks threads their differing values through the
predecessors' terminators as new successor operands, but the only
legality question asked of a predecessor was whether its terminator
implements `BranchOpInterface` (`ableToUpdatePredOperands`). The
transform's implicit assumption is that such a terminator can forward
operands of **any** type — false for dialects whose branch ops constrain
successor operand types. The LLVM dialect terminators declare theirs as
`Variadic<LLVM_Type>`, so merging two blocks that differ in, say, an
index-typed operand rewrote a verifying `llvm.cond_br` into one that no
longer verifies.
Reproducer (mixed-dialect IR of the kind a progressive lowering/raising
pipeline carries), via `mlir-opt
-pass-pipeline='builtin.module(func.func(canonicalize{region-simplify=aggressive}))'`:
```mlir
func.func @f(%m: memref<4xf32>, %c: i1) {
[33 lines not shown]
