It's extremely disturbing to see literally all foundational projects succumbing to the slop-monster. It's only a matter of time now until the critical mass of hard to detect bugs accumulate in the project, making gcc completely unusable for any practical purpose. What's worse - those will be subtle bugs The kind you get from having a defective RAM chip, somewhere in the upper addresses. And if we can't trust the compiler, we can't trust anything compiled with it.

▲

haywalk 9 hours ago | parent [-]

> succumbing to the slop-monster

So, in your view, banning vibecoded slop contributions is "succumbing to the slopmonster?"

> critical mass of hard to detect bugs accumulate in the project

Their announcement explicitly said LLMs are allowed for bug detection.

	▲	khaelenmore 9 hours ago \| parent [-]
		They only forbid what they name "legally significant". Which means that small scale contributions may still be produced by slop-machines. It's still possible to miss a bad line in this amount of code (15 lines they say). They also allow ruining test cases by slop contributions: > accept legally significant test cases that are generated by an LLM.