www/immich-public-proxy: Update to 3.4.1
- Long-press on a thumbnail enters selection mode on mobile.
- Downloads work in Chrome and Edge when an album title or filename
contains a comma.
- Downloads are named after the format Immich actually serves.
- One missing or broken video no longer stops a whole share from loading.
- Password-protected shares send Cache-Control: no-store on gallery pages,
photos and metadata.
- allowSlugLinks: false now also blocks slug links on the selective
download and metadata routes.
Changes: https://github.com/alangrainger/immich-public-proxy/releases/tag/v3.4.1
Sponsored by: Netzkommune GmbH
[flang][FIRToMemRef] Derive element strides from descriptor byte strides (#229313)
When the `fir.array_coor` base address comes out of a descriptor,
`FIRToMemRef` built each dimension's element stride as a chain of
`arith.muli` over the inner extents, even though that descriptor already
holds the dimension's cumulative byte stride. This chain grows with the
rank while reading the stride will not. This patch reads it from the
descriptor instead, as the path for descriptor-owned layouts already
does.
The division by the element size is marked `exact`, which lets it lower
to a single shift in LLVM. That is valid here because this path handles
contiguous storage, where the byte stride is the element size times the
product of the inner extents.
Follow-up: Should the division on the general descriptor path be marked
`exact` too? The conversion already needs the byte stride to be a whole
multiple of the element size, since memref strides count elements, and
it bails out on the derived-type component projections that can break
that. I left it alone to keep this patch narrow, but can expand it if
that reasoning holds.
[mlir][vector] Update doc for vector.broadcast (nfc) (#228727)
See the example below for an illustration of the newly added formula.
**EXAMPLE by @FedericoBruzzone**
Consider, for instance,
```mlir
vector.broadcast %in: vector<2x3xi32> to vector<4x2x3xi32>
```
In this case,
* `rank(source) = N = 2` and `rank(result) = K = 3`.
* `i in `[1, 2, 3]` (result idxs) and `j in [1, 2]` (source idxs),
* For `N-K < i <= N`, the corresponding source dim is `j = i + K - N`.
* For `1 <= i < N - K`, there are no source dims corresponding to `i`.
The question is:
* **Given an element of result, what is its corresponding coordinate in
[18 lines not shown]
[TableGen] Emit bytecode table for AsmWriter overflow instructions (#218530)
For targets with many instructions (NVPTX in particular), the overflow
switch emitted inside printInstruction() for operand sequences that do
not fit in the 64-bit table-driven printer can grow large enough (over
15,000 lines for NVPTX)
to trigger:
- MSVC C1001/C1053 ICE on AArch64 (function body too large)
- R_RISCV_JAL relocation truncated to fit (JAL ±1 MB range exceeded)
This patch adds an opt-in UseBytecode bit to AsmWriter (enabled for
NVPTX) that replaces the overflow switch in printInstruction() with two
function-local static const arrays and a small bytecode interpreter
loop:
- OpcodeToOffset[]: maps each instruction opcode to its starting offset
in OverflowProgram (or 0 for non-overflow instructions).
- OverflowProgram[]: stores deduplicated bytecode sequences of
operand-printing commands terminated by 1 ("return;").
[8 lines not shown]
AArch64/GlobalISel: Mark ptrauth pseudo clobbers dead (#229701)
The AUT/PAC pseudos clobber x16, x17 and NZCV. Only the register holding
the authenticated value is read afterwards; the rest of the clobbers are
dead. SelectionDAG already marks them through InstrEmitter, so do the
same in the GlobalISel selector instead of leaving them to be recomputed
later.
Co-authored-by: Claude Opus 5 <noreply at anthropic.com>
Co-authored-by: Claude Opus 5 <noreply at anthropic.com>
contrib/kyua: commit Makefile changes for version update
This was accidentally missed in the version update.
MFC after: 1 month
Fixes: eb8f69902 ("contrib/kyua: update to 0.15.0")
contrib/kyua: commit Makefile changes for version update
This was accidentally missed in the version update.
MFC after: 1 month
Fixes: eb8f69902 ("contrib/kyua: update to 0.15.0")
[lldb-server] Handle jThreadExtendedInfo (#227472)
`jThreadExtendedInfo` is already documented in the GDB remote protocol
extensions, but only `debugserver` implemented it. `lldb-server` didn't.
This implements it in `lldb-server` based on
`NativeThreadProtocol::GetExtendedInfo`.
The extended thread info is only used for Windows threads right now, so
I added a test for Windows.
contrib/kyua: update to 0.15.0
This new release contains multiple feature updates and bugfixes. Please
see the release notes mentioned in the merge commit for more details.
MFC after: 1 month
Merge commit '144afd05f8a2300361ec30c1c2020e4022ddd943'
Conflicts:
contrib/kyua/cli/cmd_debug.cpp
contrib/kyua/doc/kyua-debug.1.in
contrib/kyua/doc/kyuafile.5.in
contrib/kyua/engine/config.cpp
contrib/kyua/engine/execenv/execenv.cpp
contrib/kyua/engine/execenv/execenv.hpp
contrib/kyua/engine/execenv/execenv_host.hpp
contrib/kyua/engine/requirements.cpp
contrib/kyua/engine/requirements.hpp
contrib/kyua/engine/scheduler.cpp
[8 lines not shown]
contrib/kyua: update to 0.15.0
This new release contains multiple feature updates and bugfixes. Please
see the release notes mentioned in the merge commit for more details.
MFC after: 1 month
Merge commit '144afd05f8a2300361ec30c1c2020e4022ddd943'
Conflicts:
contrib/kyua/cli/cmd_debug.cpp
contrib/kyua/doc/kyua-debug.1.in
contrib/kyua/doc/kyuafile.5.in
contrib/kyua/engine/config.cpp
contrib/kyua/engine/execenv/execenv.cpp
contrib/kyua/engine/execenv/execenv.hpp
contrib/kyua/engine/execenv/execenv_host.hpp
contrib/kyua/engine/requirements.cpp
contrib/kyua/engine/requirements.hpp
contrib/kyua/engine/scheduler.cpp
[8 lines not shown]
