|author||Siddhesh Poyarekar <email@example.com>||2017-06-15 15:12:54 +0530|
|committer||Siddhesh Poyarekar <firstname.lastname@example.org>||2017-06-15 15:12:54 +0530|
Enable tunables by default
All of the major architectures are adopting tunables as a way to add tuning to the library, from hwcap_mask for aarch64 to HLE for s390 and ifunc and cache geometry for x86. Given this adoption and the fact that we don't want additional tuning knobs to be added outside of tunables, it makes sense to enable tunables by default using this trivial patch. Smoke tested on x86 to ensure that tunables code was built without specifying it as a configure flag. I have kept it as --enabled and not changed it to --disable since we want to still keep the option of different kinds of front-ends for tunables. * configure.ac(--enable-tunables): Enable by default. * configure: Regenerate. * NEWS: Mention change. * manual/install.texi (enable-tunables): Adjust documentation. * INSTALL: Regenerate.
Diffstat (limited to 'INSTALL')
1 files changed, 8 insertions, 10 deletions
@@ -177,18 +177,16 @@ will be used, and CFLAGS sets optimization options for the compiler.
Tunables support allows additional library parameters to be
- customized at runtime. This is an experimental feature and affects
- startup time and is thus disabled by default. This option can take
- the following values:
- This is the default if the option is not passed to configure.
- This disables tunables.
+ customized at runtime. This feature is enabled by default. This
+ option can take the following values:
- This is the default if the option is passed to configure.
- This enables tunables and selects the default frontend
- (currently 'valstring').
+ This is the default if no option is passed to configure. This
+ enables tunables and selects the default frontend (currently
+ This option disables tunables.
This enables tunables and selects the 'valstring' frontend for