> Completely different set of command line options from gcc and clang, but that's fine.

Clang does have clang-cl with similar command-line options.

At least you can use the compiler/linker without them.

Probably not. This isn't prime time TV, some foul language is tolerated - but complaining about down-votes, especially preemptively, has a predictable response (IMO rightfully so).

No complaints about down votes, simply warning the OP that (s)he will be getting some. Personally I quite like them, they indicate that I've irritated a Rust evangelist; that gives me a warm feeling inside.

Sure but being inspired by something doesn't mean you have to cargo cult the worst aspects of it.

You can have your own binary host or even just compile packages on another host on demand. -march=native is a concern in both cases.

They are shipped to a new system when you upgrade because reinstalling is for suckers.

> Not the OP, but: -march says the compiler can assume that the features of that particular CPU architecture family, which is broken out by generation, can be relied upon. In the worst case the compiler could in theory generate code that does not run on older CPUs of the same family or from different vendors.

Or on newer CPUs of the same vendor (e.g. AMD dropped some instructions in Zen that Intel didn't pick up) or even in different CPUs of the same generation (Intel market segmenting shenanigans with AVX512).

Why is it dumb?

It's not available to new users (I think there is a "karma" threshold but not sure about the exact number) and you need to to a direct link to the comment (e.g. click the time in the comment header) to see the option.

And in soviet Russia you can criticize the government all you want --- as long as you're criticizing the American government.