[ValueTracking] Extend computeConstantRange for add/sub, sext/zext/trunc
Recursively compute operand ranges for add/sub and propagate ranges
through sext/zext/trunc.
For add/sub, the computed range is intersected with any existing range
from setLimitsForBinOp, and NSW/NUW flags are used via addWithNoWrap/
subWithNoWrap to tighten bounds.
The motivation is to enable further folding of reduce.add expressions
in comparisons, where the result range can be bounded by the input
element ranges.
net/freerdp: Fix version
Upstream forgot to update version string for release 2.11.8.
net/guacamole-server broken:
configure: error:
--------------------------------------------
You are building against a development version of FreeRDP. Non-release
versions of FreeRDP may have differences in behavior that are impossible to
check for at build time. This may result in memory leaks or other strange
behavior.
*** PLEASE USE A RELEASED VERSION OF FREERDP IF POSSIBLE ***
If you are ABSOLUTELY CERTAIN that building against this version of FreeRDP
is OK, rerun configure with the --enable-allow-freerdp-snapshots
--------------------------------------------
2.11.7 => 2.11.8-dev
https://github.com/FreeRDP/FreeRDP/commit/a383740a2f85fa93f390181e5ea4bd1458b34051
[8 lines not shown]
[NFCI][analyzer] Spread use of CoreEngine::makeNode (#183540)
Simplify the code of `CoreEngine` by using the method
`CoreEngine::makeNode` (which was introduced recently in commit
1a81673922a3f5b75f342e416e925a69822c4613) and removing two similar, but
less practical utility methods.
This is technically speaking not an NFC change, because previously these
were able to generate non-sink nodes with `PosteriorlyOverconstrained`
state (which is logically unsound) and now the check in `makeNode`
prevents that.
However I labelled this as an NFCI change, as I'm fairly confident that
this won't lead to any observable changes because:
- `PosteriorlyOverconstrained` states are very rare.
- A state derived from a `PosteriorlyOverconstrained` state is also
posteriorly overconstrained, so even without this commit
`PosteriorlyOverconstrained` paths would been sunk soon at the next
transition that properly checks for it.
[5 lines not shown]
[llvm/docs] Add advanced RTTI techniques to HowToSetUpLLVMStyleRTTI (#181863)
The `HowToSetUpLLVMStyleRTTI.rst` document contained a TODO requesting
documentation for advanced RTTI usage, such as the `isa_impl` and
`simplify_type` templates. This patch resolves and removes that TODO by
adding the relevant usage introductions for `simplify_type`.
Since `isa_impl` will be moved to `namespace detail` in the future we
are not including it in the documentation.
CC: @nikic @zwuis
Signed-off-by: Lidong Yan <yldhome2d2 at gmail.com>
wireshark: updated to 4.6.4
4.6.4
Bug Fixes
wnpa-sec-2026-05 USB HID dissector memory exhaustion. Issue 20972. CVE-2026-3201.
wnpa-sec-2026-06 NTS-KE dissector crash. Issue 21000. CVE-2026-3202.
wnpa-sec-2026-07 RF4CE Profile dissector crash. Issue 21009. CVE-2026-3203.
The following bugs have been fixed:
Wireshark doesn’t start if Npcap is configured with "Restrict Npcap driver’s Access to Administrators only" Issue 20828.
PQC signature algorithm not reported in signature_algorithms. Issue 20953.
Unexpected JA4 ALPN values when space characters sent. Issue 20966.
Expert Info seems to have quadratic performance (gets slower and slower) Issue 20970.
IKEv2 EMERGENCY_CALL_NUMBERS Notify payload cannot be decoded. Issue 20974.
TShark and editcap fails with segmentation fault when output format (-F) set to blf. Issue 20976.
Fuzz job crash: fuzz-2026-02-01-12944805400.pcap [Zigbee Direct Tunneling Zigbee NWK PDUs NULL hash table] Issue 20977.
Wiretap writes pcapng custom options with string values invalidly. Issue 20978.
RDM status in Output Status (GoodOutputB) field incorrectly decoded in Art-Net PollReply dissector. Issue 20980.
[6 lines not shown]
net/freerdp: Fix version
Upstream forgot to update version string for release 2.11.8.
net/guacamole-server broken:
configure: error:
--------------------------------------------
You are building against a development version of FreeRDP. Non-release
versions of FreeRDP may have differences in behavior that are impossible to
check for at build time. This may result in memory leaks or other strange
behavior.
*** PLEASE USE A RELEASED VERSION OF FREERDP IF POSSIBLE ***
If you are ABSOLUTELY CERTAIN that building against this version of FreeRDP
is OK, rerun configure with the --enable-allow-freerdp-snapshots
--------------------------------------------
2.11.7 => 2.11.8-dev
https://github.com/FreeRDP/FreeRDP/commit/a383740a2f85fa93f390181e5ea4bd1458b34051
[7 lines not shown]
chat/matrix-synapse: Rotorill comments about upstream dependency management
- setuptools_rust (not actually needed)
- pyrsistent (jsonschema used to use it, but synapse fails to start
without it)
Despite the big diff, this is a comment-only change.
[SPIRV] Fix disabling of default extensions (#183325)
If you pass `-ExtName` to the `--spirv-ext` command line option. that
should disable the extension. However some vendors have some extensions
enabled by default when using a triple with that vendor, and disabling
an extension with the option did not effect the default extensions.
This PR makes it so disabling an extension with the `--spirv-ext` option
actually disables the extension.
The problem was we only considered the disabled extension when parsing
the arguments for `--spirv-ext`, but the default extensions are added
separately, so we need to store the disabled extensions and factor them
in when computing the final extension set to use.
Signed-off-by: Nick Sarnie <nick.sarnie at intel.com>
ValueTracking: Special case fmul by llvm.amdgcn.trig.preop
This is another instance of the logic from #183159. If we know
one source is not-infinity, and the other source is less than or
equal to 1, this cannot overflow. Special case llvm.amdgcn.trig.preop,
as a substitute for proper range tracking. This almost enables pruning
edge case handling in trig function implementations, if not for the
recursion depth limit (but that's a problem for another day).
ValueTracking: Teach computeKnownFPClass that multiply by <=1 cannot overflow
If one operand is known not-inf, that can be propagated if the other operand is
known to have a magnitude <= 1.
This enables elimination of some inf checks inside the implementation of trig
functions when the input is known not-inf.
