[LoongArch] Add patterns for vector bitwise selection (#193753)
Add instruction selection patterns for VBITSEL_V/XVBITSEL_V and
VBITSELI_B/XVBITSELI_B to match the canonical bitwise select idiom:
`(a & b) | (~a & c)`
This enables the backend to generate dedicated bitwise select
instructions instead of separate AND/ANDN/OR sequences.
py-pydantic-settings: updated to 2.14.0
2.14.0
Fix parsing env vars into Optional Strict types
Fix RecursionError with mutually recursive models in CLI
Fix env_file from model_config ignored in CliApp.run()
Update dependencies
Add Dependabot configuration
Bump samuelcolvin/check-python-version from 4.1 to 5
Bump actions/upload-artifact from 4 to 7
Bump actions/checkout from 4 to 6
Bump astral-sh/setup-uv from 5 to 7
Bump actions/setup-python from 5 to 6
Ignore chardet and group GitHub Actions in Dependabot
Bump actions/download-artifact from 4 to 8 in the github-actions group
Bump the python-packages group with 2 updates
Support reading .env files from FIFOs (e.g. 1Password Environments)
Fix AliasChoices ignored when changing provider priority
[20 lines not shown]
[libc++] Refactor std::print to allow for constant folding of the format part (#185459)
```
---------------------------------------------------------
Benchmark old new
---------------------------------------------------------
std::print("Hello, World!") 43.6 ns 9.88 ns
```
[mlir][spirv] Tighten SPIR-V TOSA convolution verification (#194592)
Add verifier coverage for SPIR-V TOSA convolution ops against the TOSA
shape and type constraints.
This adds shared TableGen shape predicates for Conv2D, Conv3D,
DepthwiseConv2D and TransposeConv2D, including batch/channel/bias
relationships. It also constrains integer convolution weights so i8 and
i16 inputs use i8 weights, matching the SPIR-V TOSA representation.
Add custom verifiers for the convolution output shape formulas,
including stride divisibility for regular convolutions and out_pad
bounds for TransposeConv2D. Tighten pad, stride and dilation attributes
to use non-negative or positive i32 attribute constraints where
required.
Signed-off-by: Davide Grohmann <davide.grohmann at arm.com>
[KnowFPClass] Refactor fmul & fdiv (NFC) (#191651)
- Remove `0 * Inf -> NaN` redundant check and a nan setting.
The reason:
```rust
1. Inf * Y -> {Inf, NaN}
2. 0 * Y -> {Zero, NaN}
3. 0 * Inf -> NaN
```
But after `1.` and `2.` we already have `{Inf, NaN} ∩ {Zero, NaN} ->
NaN`
So `3.` is redundant and [can be
removed](https://github.com/llvm/llvm-project/pull/191651/changes#diff-eacbd8c8620db92a00453be14b3b433c618946ad7b57c10b039437641e9777c4L389):
```diff
// +/-0 * +/-inf = nan
- if ((KnownLHS.isKnownAlways(fcZero | fcNan) &&
- KnownRHS.isKnownAlways(fcInf | fcNan)) ||
- (KnownLHS.isKnownAlways(fcInf | fcNan) &&
[4 lines not shown]
[SCEV] Limit ControlsOnlyExit logic to BinOps with neutral elements. (#194831)
As far as I can tell, ControlsOnlyExit is used during reasoning to
assume
that we stay in the loop as long as the condition is true/false, and are
guaranteed to exit otherwise.
But unless I am missing something, a sub-condition of an AND/OR never
solely controls the exit, whether we exit always depends on both
conditions.
Pass false to ControlsOnlyExit, as otherwise we would incorrectly assume
that we must exit if either conditions is true, when we would only exit
if both are true.
For now, ControlsOnlyExit is only used for the neutral element case, it
may be worth removing this.
Alive2 proof of IndVars mis-compile: https://alive2.llvm.org/ce/z/kWs4hE
PR: https://github.com/llvm/llvm-project/pull/194831
postgresql-timescaledb: updated to 2.26.4
2.26.4
Sanitize `DT_NOBEGIN` next_start to recover jobs stuck after primary failover
Fix `now()` constification for continuous aggregate queries
Fix out of memory when propagating `ALTER TABLE` to many chunks
Fix `InstrStartNode` called twice in a row
Fix use-after-free of `PlaceHolderVar.phrels` in cached ChunkAppend plans
Fix `PlaceHolderVar` error in runtime chunk exclusion
Remove stale hypertable entries during upgrade
Fix segfault with transition tables after column drop
Use `DROP CASCADE` for trigger removal
Error when querying compressed chunks under Apache license
Make `timescaledb_post_restore()` reliably restart background workers in a single call
Fix lost orderby sparse index
Replace `ERRCODE_INTERNAL_ERROR` on user-reachable error paths
Add Error on missing custom job function in `ts_bgw_job_get_funci`
Fix data corruption when merging chunks with different compression settings
[5 lines not shown]
dev/ichsmb: disable block buffer if supported
In order to improve the efficiency of block read/write calls, Intel has
introduced a block buffer. Instead of generating an interrupt after
receiving/sending a single byte, the data is buffered in the block buffer. It
allows the SMBus controller to generate a single interrupt for the whole
transfer. At the moment, we don't support that and don't expect the SMBus
controller to behave in that way. Unfortunately, BIOS code can also access the
SMBus controller and may enable the block buffer. Poorly written BIOS code may
also keep the block buffer enabled breaking our driver. Therefore, we should
check if the device supports a block buffer and disable it for every request
because we don't know if some BIOS code has reconfigured the SMBus controller
in between.
Reviewed by: emaste
MFC after: 1 week
Sponsored by: Beckhoff Automation GmbH & Co. KG
Pull Request: https://github.com/freebsd/freebsd-src/pull/2161
libgsf: updated to 1.14.57
1.14.57
* Fix problems with ole files bigger than 4G.
* Document property fix.
* Introspection fixes.
* Make gzip, bzip, zip handle 4G+ writes.
* Make gzip, bzip, zip handle 4G+ reads.
* Improve testing.
* Ole performace improvements with loads of children.
bhyve: allow read/write to full CRB buffer
For some reason, we've incorrectly calculated the size of the CRB data buffer
register. There's no need to divide the CRB data buffer size by 4. We should
allow access to the whole buffer instead.
Reviewed by: markj
MFC after: 1 week
Sponsored by: Beckhoff Automation GmbH & Co. KG
Pull Request: https://github.com/freebsd/freebsd-src/pull/2169
[SelectionDAG][AArch64] Legalize vector.[de]interleave6 (#193723)
With #192972 and #192677 merged, [de]interleave6 can also benefit from
the existing legalization work from #141513
llvm: Use add_link_options for stack size flags (#195034)
Previously, LLVM was directly editing `CMAKE_EXE_LINKER_FLAGS`. This is
a user-facing CMake cache variable not meant to be modified by project
code. This was causing issues for downstream consumers building
non-C/C++ targets as part of the LLVM build.
Modern CMake provides `add_link_options()`, a cleaner way to set linker
flags that propagate to every target in a directory tree.
Generator expressions and the `LINKER:` prefix syntax ensure that this
is only applied to executable targets with the proper language and
linker argument wrapping.
[libc++] Remove libc++'s own inttypes.h (#193716)
The header does three things:
- it defines `__STDC_FORMAT_MACROS` for compatibility with glibc
versions we don't support anymore
- it includes `<stdint.h>`, which is already required to be included by
the C standard
- it `#undef`s two macros which might be defined by the libc. We don't
provide a `<stdint.h>` header ourselves, which might provide these
macros as well, so these are already not defined by any libcs we
support.
So this header should be safe to remove.
ipsec: allow headers to be 'static'
Interesting but where false/true is not 'false'/'true' as we
are dealing with strings rather than booleans when using ==
[clang][bytecode] Reject uninitialized bases in builtin_bit_cast (#194625)
Like the current interpreter does. Also use the bytecode interpreter in
the test in SemaCXX/.