rbdoom3: Option to set CPU_ID and to specify CPU Features to be used.

[coldtobi]

The goal for those patches is again for Debian :) To honour the baseline CPU functions we are allowed to use and also allow to compile on other architectures.

The pull requests adds two options to the build-system:
CPU_TYPE -- When set, passes this string as CPU-ID, which will be embedded into the binary. If unset, the code decides (but only for i386 and amd64).

In Debian I will set it to $(DEB_BUILD_ARCH_CPU)

CPU_OPTIMIZATION Which CPU specific optimitations should be used beside the compiler's default?
default: "-mmmx -msse -msse2" (defaults to the same as your repository)

For Debian I will use the compiler's default, means setting this to an empty string.

USE_INTRINSICS will be progated to the build system only if explictly disabled -- this will disable usage of the intrinsics which are not available on most archs.mmx

For Debian I will use the intrinsics only on amd64.

tobi

[BielBdeLuna]

is this to compile exclusive for the CPU you have in the computer?

[coldtobi]

Am Freitag, den 19.06.2015, 08:22 -0700 schrieb Biel Bestué de Luna:

is this to compile exclusive for the CPU you have in the computer?

---

Reply to this email directly or view it on GitHub:
#228 (comment)

No, it is not targeting a specific CPU. This enhances portability and
make sure that features I cannot use or are not available for a specific
architecture are not used when creating the Debian package.

Compare:
Without patch:
https://buildd.debian.org/status/logs.php?pkg=rbdoom3bfg&ver=1.0.3%
2Brepack1-3&suite=sid

With patch:
https://buildd.debian.org/status/logs.php?pkg=rbdoom3bfg&ver=1.0.3%
2Brepack1-4&suite=sid

(I'm also working to enable the remaining archs, but one step after the
other; I will create dedicated pull requests for that)

tobi