[VPlan] Fix wrap-flags on WidenInduction unroll (#187710)
Due to a somewhat recent change, IntOrFpInduction recipes have
associated VPIRFlags. The VPlanUnroll logic for WidenInduction recipes
predates this change, and computes incomplete wrap-flags: update it to
simply use the flags on IntOrFpInduction recipes; PointerInduction
recipes have no associated flags, and indeed, no flags should be used.
Update to 1.25
Upstream changes:
1.25 2026-02-13 <schubiger at cpan.org>
- Merged development version to stable.
1.24_01 2026-02-12 <schubiger at cpan.org>
- Add parsing for beginning and end of x months ago, this month,
and x months from now. [github #28 - gibus]
1.24 2026-01-18 <schubiger at cpan.org>
- Merged development version to stable.
1.23_03 2026-01-13 <schubiger at cpan.org>
- Don't use _{set,get}_truncated() when no value is truncated.
- Use hash slices instead of passing values one by one.
1.23_02 2026-01-12 <schubiger at cpan.org>
- Support fractional seconds in iso8601 strings.
[github #27 - isla w]
1.23_01 2026-01-09 <schubiger at cpan.org>
- Support optional time zone information in iso8601 time strings.
[github #26 - isla w]
[10 lines not shown]
Update to 0.19
Upstream changes:
0.19 2026-03-12
- Release version 0.18-TRIAL as production release.
- 0.18-TRIAL Fixed an issue calculating nanoseconds on certain architectures where the precision
of integers caused the nanoseconds calculation to round incorrectly. Occurred on
Raspberry Pi with -Duselongdouble (arm64). Fixed by @timlegge (Timothy Legge).
Fixes GH #16 via PR #19.
0.18 2026-03-10 (TRIAL RELEASE)
- Fixed an issue calculating nanoseconds on certain architectures where the precision
of integers caused the nanoseconds calculation to round incorrectly. Occurred on
Raspberry Pi with -Duselongdouble (arm64). Fixed by @timlegge (Timothy Legge).
Fixes GH #16 via PR #19.
radvd: match radvd_enable() more closely for #10044
Users are confused why they can add an entry but their settings are not
being used. This is specifically wrong according to the inventor of
"dhcpd6track6allowoverride" as it circumvents half of its use cases but
more closely matches user expectation.
May cause regression for some people, but not much we can do here other
than not doing it.
[clang][analyzer] Add location to CTU failure diagnostics
Report CTU import failures at the place where the imported symbol would
be used. This helps to quicker understand why CSA might miss a certain
expected CTU bug.
--
CPP-7804
[LoopUnroll] Use MapVector for deterministic iteration order. (#188821)
NonLoopBlocksIDom determines the order we adjust the DT, impacting DRT
child ordering.
Similarly, ExitInfos order impacts the order of SetDest, which applies
DT updates.
The order impacts collectChildrenInLoop, which in turn impacts the we
process BBs in LICM. And this in turn impacts the order in which we
perform alias queries.
If the order is not deterministic, we sometimes get different NumNoAlias
statistic counts for the same input, and possibly also different IR,
although I have not confirmed the latter.
Compile-time impact is neutral:
https://llvm-compile-time-tracker.com/compare.php?from=77710f14202a8684e12d68d08d2cd3738bbd0e1d&to=066ac6284041aac454c8ffa2894b866acbf96fd3&stat=instructions:u
[3 lines not shown]
[VPlan] Don't set WrapFlags for truncated IVs. (#188966)
The wrap flags from the IV bin-op are not guaranteed to apply to
truncated inductions, which are evaluated in narrower types.
Instead of dropping them late (in expandVPWidenIntOrFpInduction), do not
add them at the outset, the prevent invalid transforms based on
incorrect flags in the future.
PR: https://github.com/llvm/llvm-project/pull/188966
Firewall: Remove tokenizer from categories and use selectpicker instead (#10049)
The issue with the tokenizer is the limit of items that is set to 10 per default, which does not always display all items. And you can increase it, but that also needs CSS changes. Additionally the tokenizer is not maintained anymore, and needs replacement. Cutting it out here decreases the need to clean this up later.
The fix here is that now all categories will be displayed and are searchable via the normal selectpicker search field.
Make pthread_mutex_destroy() not error out for mutexes that were initalized
with PTHREAD_MUTEX_INITIALIZER but not used.
Unify handling of mutexp == NULL in both version of pthread_mutex_destroy()
and ensure that *mutexp == NULL is not considered an error.
Problem found by tb@ with rpki-client.
OK kettenis@ tb@
