Compiling SDL on SPARC platform with GNU toolset should target correct CPU by default

[joncox123]

Compiling SDL on SPARC platform with GNU toolset should target correct CPU by default

[madebr]

Adding hardware specific flags like -mcpu=..., -march=..., -mtune=... does not belong in a build system.
In autotools land, users should configure their CFLAGS/CPPFLAGS correctly.
In CMake land, users should use an appropriate CMake toolchain file (and don't worry about -mcpu=... at all)

In the same vain I also don't think we should print a warning when no -mcpu=... command can be found in the CFLAGS.
It does not scale to other projects. You can't expect every OSS project to do these checks.

I think extending system-wide autotools/cmake rules makes more sense.

[smcv]

Adding hardware specific flags like -mcpu=..., -march=..., -mtune=... does not belong in a build system.

I agree. With my Debian hat on, we have recurring problems with upstream projects (in the same position as SDL) saying something like "well obviously nobody will run my software on an x86 without SSE" or "well obviously nobody will run my software on an ARM without NEON" and hard-coding their own -mcpu or -march which is higher than the baseline that Debian has chosen to make its minimum for a particular architecture, resulting in binaries that crash with an illegal instruction on baseline CPUs.

Choosing the baseline is something to be done by OS builders, not by individual upstream projects that become part of your OS or are compiled as addons to your OS. It should be possible to configure gcc at the time that you build gcc to have a particular baseline of your choice (definitely true on x86 and ARM, probably equally true on SPARC), so that all software that you build with that gcc binary will automatically assume that baseline unless forced to behave otherwise by options like -march. I would suggest doing that.

[icculus]

Sounds like this is a WONTFIX. Those that are building can configure/cmake with CFLAGS="-mwhatever" and get what they want.