If it's a real bug, you can just report what you know and leave it at that. You don't need to embellish it with random guesses about a root cause.

Okay: "I compile this input and the linker crashes."

Not okay: "I compile this input and the linker crashes. Also here's 10 paragraphs of slop about dwarf tables, which I can't even evaluate the accuracy of since I'm not an expert."

> Typically, any time you think you've found a compiler error, you're using it wrong...

Yes, if you can't figure out if it's a bug, the bug tracker is the wrong place to get help. Ask in a community forum instead.

▲

onlyrealcuzzo 37 minutes ago | parent [-]

> Not okay: "I compile this input and the linker crashes. Also here's 10 paragraphs of slop about dwarf tables, which I can't even evaluate the accuracy of since I'm not an expert."

It's a 20-line file with a few commands to run it to reproduce it. Not 10 paragraphs of slop.

Presumably that is much more helpful than - here's my gigantic repo, good luck running my tests, also good luck finding the bug.

	▲	nvme0n1p1 30 minutes ago \| parent [-]
		> here's my gigantic repo, good luck running my tests What about my comment made you think I was suggesting not to give repro steps? > also good luck finding the bug But yes actually, this half is true. It's better to give them no extra information, than to give too much information that you have no idea if it's true or not.