https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112286
--- Comment #5 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- (In reply to chenglulu from comment #4) > (In reply to Xi Ruoyao from comment #2) > > (In reply to chenglulu from comment #1) > > > (In reply to Robin Lee from comment #0) > > > > Follow-up from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682#c2 > > > > > > > > libgo runtime needs an update. > > > > gccgo build scripts need to support loongarch64. > > > > > > Do I have to use gccgo? Since the version of go in gcc is relatively low, > > > this transplant requires some work. > > > > GCC will eventually bump the Go version but it requires some non-trivial > > work: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682#c6. So I'd like > > to defer the transplant after Ian completes all these. > > Do you know when the version of gccgo will be upgraded? No but anyway we should be struggling to make it match the latest Google Go compiler. If we cannot keep up one day I guess gccgo will be simply removed.
