Στις Παρ, 11 Δεκ 2020 στις 10:02 μ.μ., ο/η Segher Boessenkool < seg...@kernel.crashing.org> έγραψε:
> Hi! > > Thanks for trying to push this forward. > > On Fri, Dec 11, 2020 at 09:49:18PM +0200, abebeos via Gcc-patches wrote: > > Στις Παρ, 11 Δεκ 2020 στις 8:32 μ.μ., ο/η Jeff Law <l...@redhat.com> > έγραψε: > > > On 12/9/20 6:12 AM, abebeos via Gcc-patches wrote: > > saaadhu (1st choice, zero regressions) should have one, has recently > > commited something, too: > > > > > https://gcc.gnu.org/git/?p=gcc.git;a=search;h=e7d55c6b81733335d81e35f7c0116bbdffccb682;s=Senthil+Kumar+Selvaraj;st=committer > > Yes, he is in MAINTAINERS. > > > Second, the work needs to be submitted for inclusion. I don't recall > > > seeing an official submission from either of them to gcc-patches. > > > > My understanding of "non-FSF world-legals" is that something that is > > already released/assigned needs no submission. > > It's not just that: all patches should hit gcc-patches@. For > transparency, and so that everyone can easily comment on it. > > If someone has published a modified GCC anywhere public, anyone can > take that code. That is how the GPL works. > > But we still need it on gcc-patches to review it :-) > Ok, to speed things up, is it ok if I simply pick the patch that I've attached to the issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c21 and post it here to the gcc-patches list within at [PATCH] tagged new topic? I'd ask the original author, but it seems he's busy with other work, so to avoid delays... > Segher >
