They can just fork off the Golang frontend and it would be the same, maybe patch the runtime a bit.

Being an old dog, as I mention elsewhere, I see a pattern with gcj.

GCC has some rules to add, and keep frontends on the main compiler, instead of additional branches, e.g. GNU Pascal never got added.

So if there is no value with maintenance effort, the GCC steering will eventually discuss this.

▲

MangoToupe 7 hours ago | parent | prev [-]

Does gcc even support go?

▲

wahern 7 hours ago | parent | next [-]

Until a few years ago, gccgo was well maintained and trailed the main Go compiler by 1 or 2 releases, depending on how the release schedules aligned. Having a second compiler was considered an important feature. Currently, the latest supported Go version is 1.18, but without Generics support. I don't know if it's a coincidence, but porting Generics to gccgo may have been a hurdle that broke the cadence.

▲

ratmice 6 hours ago | parent [-]

Seems doubtful, given that generics and the gccgo compiler were both spearheaded by Ian Lance Taylor, it seems more likely to me that him leaving google would be a more likely suspect, but I don't track go.

	▲	pjmlp 5 hours ago \| parent [-]
		This has been stagnant long before he left.

▲

ameliaquining 7 hours ago | parent | prev [-]

Yes, though language support runs behind the main Go compiler. https://go.dev/doc/install/gccgo