[mlir][spirv] Tighten SPIR-V TOSA pool constraints (#193515)
Tighten AvgPool2D and MaxPool2D verification by constraining kernel,
stride, and pad attributes and by checking the input/output NHWC
relationship.
Add verification tests for batch/channel mismatches, non-divisible
pooled shapes, pad-vs-kernel failures, and incorrect output shapes.
Signed-off-by: Davide Grohmann <davide.grohmann at arm.com>
[LLVM][SelectionDAG] Don't assume masked loads access all lanes in memory. (#192706)
When creating the initial DAG for masked loads we are using the result
type to define LocationSize. However, being a masked load we do not know
which, if any, memory locations will be read.
Fixes https://github.com/llvm/llvm-project/issues/180251
[flang][NFC] Converted five tests from old lowering to new lowering (part 49) (#194276)
Tests converted from test/Lower: pointer-initial-target-2.f90,
pointer-initial-target.f90, pointer-references.f90,
pointer-results-as-arguments.f90, pointer-runtime.f90
chroot.2: "filedescriptors" => "file descriptors"
"filedescriptors" is the odd one out when looking at other manual pages.
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
[Clang] No longer advertise support for coroutines on x86 windows. (#193456)
There are a large number of long standing issues with coroutines on
x86_32 windows as discussed here
https://github.com/llvm/llvm-project/issues/59382
- #59382
- #58556
- #58543
- #56989
- #193161
- #136481
As such this patches
- No longer defines `__cpp_impl_coroutine` on that platform
- Warn when using coroutines on that platform
The reason to not plainly error is that it would break too much valid
[7 lines not shown]
Handle IMPLICIT_DEF in TripleMBB for WindowScheduler (#179190)
Previously, IMPLICIT_DEF instructions were not copied into the
triple-MBB region used by the WindowScheduler. This left the
machine-level liveness inconsistent with the triplicated code and could
trigger a LiveIntervals assertion:
LiveIntervals::HMEditor::updateRange: Assertion `LR.verify()' failed.
Copy IMPLICIT_DEF into the triple region so that the triplicated block
has a consistent set of defs and LiveIntervals can update ranges
correctly.
---------
Co-authored-by: Matt Arsenault <arsenm2 at gmail.com>
interfaces: wrong DUID-UUID format for #10218
Not sure about migration here to avoid future migrations from breaking,
but wrong UUID is simply wrong. To be continued.
misc/py-aider-chat: Remove port
aider-chat upstream has stopped doing releases, and its dependencies have
drifted too much to be practically maintained within the ports tree.
[memref] Simplify loads from reinterpret_cast of 1D contiguous memrefs (#188459)
Rewrite `memref.load` operations whose source is a `reinterpret_cast` that
represents a rank reshape of a 1D contiguous `memref` with a single non-unit
dimension.
Assisted-by: ChatGPT (refine implementation + tests). I reviewed all code and
tests before submission.
## Example
Before:
```mlir
%reinterpret_cast = memref.reinterpret_cast %src
to offset: [0], sizes: [1, 1, 999], strides: [999, 999, 1]
: memref<999xi64> to memref<1x1x999xi64>
%0 = memref.load %reinterpret_cast[%c0, %c0, %i]
: memref<1x1x999xi64>
```
[54 lines not shown]
NAS-140801 / 27.0.0-BETA.1 / Show downloaded size when image content-length is missing (#18809)
## Problem
When pulling a container image from the registry, if the server's HTTP
response does not include a content-length header (or returns 0), the
download progress message always displays
"Downloading image: 0.0MB" regardless of how much data has actually been
downloaded. This is because the code was using total_size_mb (which is
0.0 when content-length is absent) instead
of downloaded_size_mb.
## Solution
Use downloaded_size_mb in the progress message so users see the actual
amount downloaded so far (e.g., "Downloading image: 12.5MB") instead of
a static "0.0MB".
