https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34422
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|egallager at gcc dot gnu.org |unassigned at gcc dot
gnu.org
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #12)
> (In reply to Eric Gallager from comment #11)
> > Patch posted to gcc-patches:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596654.html
>
> So this patch needs some more work; it might take awhile before I get to
> fixing it though... should I unassign? I still intend to get back to this
> later, but I just want to make sure that people are clear that they can give
> it a try themselves in the meantime...
...ok yeah I think I'm going to unassign; if anyone thinks they can address the
feedback from here, feel free to take it:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597046.html
