On Wed, Jan 7, 2026 at 5:07 PM Jeffrey Law <[email protected]> wrote: > > > > On 1/7/2026 3:02 AM, Frank Scheiner wrote: > > Dear all, > > > > I'd like to ping the following patches. As you already pushed patches > > from us in the past, would you please have a look - if time allows? > > > > 1. https://gcc.gnu.org/pipermail/gcc-patches/2025-November/700415.html > > [PATCH] ia64: properly include libunwind support during configuration > > > > 2. https://gcc.gnu.org/pipermail/gcc-patches/2025-November/700656.html > > [PATCH 1/2] ia64: Fix zero_call_used_regs for PRs [PR121535] > > > > [PR121535]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121535#c11 > I've committed these two. > > > > > 3. https://gcc.gnu.org/pipermail/gcc-patches/2025-November/700657.html > > [PATCH 2/2] ia64: Expand MAX_VECT_LEN to 16 > It's not clear to me this is the right thing to do. It seems to me that > value should be driven by performance behavior, not as a workaround for > limitations of the middle-end diagnostics.
It's purely internal as size to local arrays in ia64 permute handling (copy&pasted from other targets I guess). So it has to match the largest mode and likely the diagnostic correctly complains it is short. So the patch looks obvious to me (for V16QI). Richard. > > jeff
