[AMDGPU] Mark CDBG branches as having side effects (#226123)
The change marks all four CDBG branch variants as having unmodeled side
effects, consistent with reading externally controlled debug state.
www/p5-CGI-Response: Mark DEPRECATED
- Switch to DISTVERSION while I am here
- Fix fetch
- Set EXPIRATION_DATE 2026-10-24
- No functional upstream release since 0.03 (1995)
- The CGI response-construction model it implements has been superseded
by PSGI/Plack in modern Perl web applications
- No consumers on the tree
(cherry picked from commit 4276b29db42a02185bde90805371c080c5c09530)
www/p5-WebService-Linode: Mark DEPRECATED
- Switch to DISTVERSION while I am here
- Set EXPIRATION_DATE 2026-10-24
- Remove stale MASTER_SITES
- Pet portclippy
- Implements Linode's legacy dot-notation API v3, deprecated by Linode
circa 2018 with new API-key generation blocked
- Author (MIKEGRB) never added APIv4 support and made no further CPAN
releases after 0.29 (2019)
- No consumers in the tree
(cherry picked from commit 5cd2067a98ea2fca2a359d88a139cdadb72cab59)
www/p5-CGI-Response: Mark DEPRECATED
- Switch to DISTVERSION while I am here
- Fix fetch
- Set EXPIRATION_DATE 2026-10-24
- No functional upstream release since 0.03 (1995)
- The CGI response-construction model it implements has been superseded
by PSGI/Plack in modern Perl web applications
- No consumers on the tree
www/p5-WebService-Linode: Mark DEPRECATED
- Switch to DISTVERSION while I am here
- Set EXPIRATION_DATE 2026-10-24
- Remove stale MASTER_SITES
- Pet portclippy
- Implements Linode's legacy dot-notation API v3, deprecated by Linode
circa 2018 with new API-key generation blocked
- Author (MIKEGRB) never added APIv4 support and made no further CPAN
releases after 0.29 (2019)
- No consumers in the tree
[X86] Prepare bdver fp<->int tests for TuningPrefer128Bit (#226121)
Ensure the check prefixes can handle bdver targets independently, I've
also reordered some of the tests so we can cleanly order the eventual
AVX128/AVX256/AVX512 checks
Help reduce the diff for #225838
[Polly] Restate array sizes and subscripts when the element type shrinks (#221496)
Polly uses the smallest type to an array with element type of its
ScopArrayInfo. So a byte-wise access, such as a memset, can make the
element type smaller after the sizes of the array dimensions have
already been stored. Those sizes were not updated when the element type
changed: a row of a two-dimensional array of double kept the size. Every
access to the array then looks like it goes past the end of its row, the
inbounds assumption becomes impossible to satisfy, and the SCoP is
dropped without any message. Finally, this patch multiplies the size of
the innermost dimension.
Assisted-by: Claude (Anthropic)