Comment # 4 on bug 1233590 from Paul Fee

> Yeah, that's accurate.

Thanks I now see the relationship between the releases/gcc-14 branch in GCC's
git repo, the 14.2 official release and Tumbleweed's 14.2.1 version.

> > perhaps I can clone GCC's public repo and attempt to bisect the issue
> Yes, that would be very nice.

Using "git bisect run" (fantastic tool), I was able to scan between the
releases/gcc-14.2.0 tag and the HEAD of the releases/gcc-14 branch.

The relevant commit is:
b5ed381d05e c++: inherited CTAD fixes [PR116276]

I also cherry-picked this into a worktree reset back to 04696df0963 (tag:
releases/gcc-14.2.0).  This applied cleanly and resolved the issue.  Suggesting
that it may be feasible to backport this into the Leap 14.2.0 package if the
project deems appropriate.