https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69058
--- Comment #6 from vries at gcc dot gnu.org --- (In reply to Thomas Schwinge from comment #5) > Isn't it a gccgo front end (spec) bug, that it doesn't bring in GOMP stuff > (builtins, link against libgomp) under the presence of > "-ftree-parallelize-loops=2"? Cf. gcc/gcc.c:GOMP_SELF_SPECS. Making parloops robust against missing libgomp support is a conservative fix for the ICE, and appropriate for stage3. Enabling parloops for go could be a stage1 effort. But (having no go knowledge whatsoever) I cannot exclude the possibility that the libgomp support is missing intentionally.
