AMDGPU: Migrate CodeGen tests to amdgpu subarch triple (37) (#209601)
Mechanically migrate the command-line target spelling on llc/opt RUN
lines in llvm/test/CodeGen/AMDGPU from -mtriple=amdgcn ... -mcpu=<gfx> to the
folded subarch triple form (e.g. -mtriple=amdgpu9.00-amd-amdhsa), dropping the
redundant -mcpu.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude-Opus-4.8)
AMDGPU: Migrate CodeGen tests to amdgpu subarch triple (36) (#209600)
Mechanically migrate the command-line target spelling on llc/opt RUN
lines in llvm/test/CodeGen/AMDGPU from -mtriple=amdgcn ... -mcpu=<gfx> to the
folded subarch triple form (e.g. -mtriple=amdgpu9.00-amd-amdhsa), dropping the
redundant -mcpu.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude-Opus-4.8)
[clang][bytecode] Fix uninitialized diagnostics (#209702)
... if the pointer is also outside its lifetime. In that case, prefer to
diagnose it as outside its lifetime.
[clang][constexpr] Move anonymous-union check before getDestructor() in HandleDestructionImpl (#197416)
When HandleDestructionImpl destroys a class object during constant
evaluation, it attempts to look up the class's destructor via
getDestructor() before checking whether the record is an anonymous
union. Anonymous unions should not have their destructors invoked
directly during constant evaluation — their lifetime is managed by the
enclosing class's destructor. Move the anonymous-union short-circuit
before the getDestructor() call so anonymous unions are handled early,
regardless of whether getDestructor() returns null or not.
This fixes cases where an object with an implicitly-defined constexpr
destructor stored inside an anonymous union member was incorrectly
rejected during constant evaluation.
[NFC][BoundsSafety] Re-order some checks in `Sema::CheckCountedByAttrOnField` (#209713)
This is post-merge feedback for #209603
(4b455a91141d59ace3a29870c885f5f5e4ff0506).
[LoongArch] Fix invalid VEXTH combines for unsupported type extensions
`matchHalfOf128BitLanes` was shared by both shift and extend combines, but it
unconditionally required LSX support, preventing valid LASX-only patterns
from matching. Make the helper check LSX and LASX requirements
independently based on the pattern being recognized.
Additionally, `performEXTENDCombine` could form `VEXTH`/`VEXTH_U` nodes for
unsupported type combinations, such as extending `v8i8` to `v8i32` or
`v2i64` to `v2i128`. These illegal nodes would later reach instruction
selection and trigger backend failures:
* `Cannot select: LoongArchISD::VEXTH`
* `Don't know how to legalize this operation`
Update hitori to 44.0
* Remove GNOME branding as it�s not an official GNOME game any more
* Bugs fixed:
- !39 Update (or drop) the Docker image used by Flatpak job
- !40 data: Remove GNOME branding
- !41 build: Post-branch version bump
- !43 flatpak: Fix the branch name for building the flatpaks
* Initial support for playing the game with a keyboard
* Bugs fixed:
- !34 Make game playable with keyboard (bare minimum)
- !35 build: Drop positional arguments from i18n.merge_file() calls
- !36 interface: Fix a minor leak
- !37 snap: Add itstool to image
- !38 Move appdata screenshot to git
plus many many translation updates.
net-mgmt/netbox: Update to 4.6.5
Changelog:
Enhancements:
* Add MDC connector type for fiber ports and cables
* Provide a REST API method to update or overwrite an existing custom
script module
* Enforce a lower maximum uploaded image size (50 megapixels) than the
Pillow default
* Add Korean language support
Performance Improvements:
* Add a prefetch hint to the GraphQL tags field to avoid N+1 queries on
list endpoints
* Cache serializers to avoid repeated reinstantiation on the cables list
REST API endpoint
Bug Fixes:
[29 lines not shown]
devel/py-rq: Update to 2.10.0
* The issues related to py-django-rq were resolved with the 4.1.1
release, so py-rq can now be updated to the latest version.
Changelog:
https://github.com/rq/rq/releases/tag/v2.10
Approved by: skreuzer (maintainer, implicit)
MFH: 2026Q3
(cherry picked from commit 5cea31387a178f9288ea41e7a9b6f5c7895ca6f5)
clang-offload-bundler: Remove conflicting-target-ID diagnostic
This was checking that you did not try to combine arches with
any mode vs. a specific mode (e.g, gfx90a and gfx90a:xnack+). I
don't see any point in this diagnostic. All the modes have a natural
interpretation as distinct targets with a selection preference. It's
more defensible to have this rule in the user facing clang driver,
but not the low level binary utilities. This reduces the surface area
of some special case target ID parsing.
Co-authored-by: Claude (Opus 4.8)
clang-offload-bundler: Fix host dependency of tests
Use an explicit linux triple for the host target instead of using the
default/host target and marking most every other system as unsupported.
Fixes not running these tests on macos.
Co-authored-by: Claude (Opus 4.8)
[Polly] Skip vectorize.enable for FP loops with dist=1 dependences (#205756)
When -polly-annotate-metadata-vectorize is active, Polly marks its
generated loops with llvm.loop.vectorize.enable=true. This is harmful
for loops with a loop-carried dependence of distance 1 that involve
floating-point operations: the Loop Vectorizer reorders FP operations
(e.g. scalar reduction like q = factor*q), producing results that differ
from the sequential scalar reference and causing correctness failures.
Two changes are made:
1. IslAst.cpp: add PollyVectorizeMetadata to the PerformParallelTest
gate so that dependence-distance computation is performed whenever
-polly-annotate-metadata-vectorize is passed, not only when
-polly-parallel or a vectorizer is active.
2. IslNodeBuilder.cpp / LoopGenerators.cpp: when a loop has a dist=1
dependence involving FP operations, omit the vectorize.enable annotation
entirely. This lets the Loop Vectorizer apply its own cost model and
legality checks decide.
[lldb][POSIX] Correctly report error copying from remote platform (#207365)
This fixes a bug I found where copying a file from a remote Linux
platform using the API would claim that it succeeded, but it had not.
The local file was read only so it was not updated. The host Linux
platform's copy did not have this bug.
There are two tests, one which will run if the testing platform is not
already a remote. This one spawns a "remote" platform, which is actually
still on the host, but it's enough to take the remote code path in the
POSIX platform implementation.
The second uses the testing platform. If that's a remote, use that, if
it's host then we use the host platform to check local copying
behaviour.
This test is not as specific as I'd like it to be, but I wanted
something that could run on many platforms. Even if the copy fails for a
reason other than permissions, at least we are checking that the failure
is propagated.
