The average bystander might want to write high-performance code for their risc-v cpu. Then they must know precisely which instructions are available and what the performance implications of using them are. E.g., the difference between a shared and non-shared fp register file is huge.

▲

rwmj 2 hours ago | parent | next [-]

For the "average bystander" they're going to buy an OS and compatible hardware, or if they're the average programmer they're going to use a compiler and libraries that solve the problem already for them. Very very few people need to worry about the details.

▲

akarpathy an hour ago | parent [-]

The average programmer still must inform their compiler what to use. Claude Code can assist with this.

	▲	andrepd an hour ago \| parent [-]
		You need Claude Code to copy a string into your config/make file?

▲

panick21_ 2 hours ago | parent | prev [-]

You think the average person writes performance optmized code?

If you are on that level then you know pretty well what you are targeting. And even then in 99% of cases you just look at the top level profile.

If you do performance analysis for some specific embeded project that is not using a standard profile, then its a bit more work, but hardly impossible.

	▲	bjourne an hour ago \| parent [-]
		Bruh, the "average person" won't buy a riscv-based computer in decades. The average bystander to the riscv project indeed writes high-performance code for their, so far, mostly non-existent or emulated riscv processors.