From 37f8abad1c7b274e66eaf2d04684bd8a7ba0bcef Mon Sep 17 00:00:00 2001 From: Adhemerval Zanella Date: Mon, 30 Jan 2017 18:07:32 -0200 Subject: nptl: Remove COLORING_INCREMENT This patch removes the COLORING_INCREMENT define and usage on allocatestack.c. It has not been used since 564cd8b67ec487f (glibc-2.3.3) by any architecture. The idea is to simplify the code by removing obsolete code. * nptl/allocatestack.c [COLORING_INCREMENT] (nptl_ncreated): Remove. (allocate_stack): Remove COLORING_INCREMENT usage. * nptl/stack-aliasing.h (COLORING_INCREMENT). Likewise. * sysdeps/i386/i686/stack-aliasing.h (COLORING_INCREMENT): Likewise. --- sysdeps/i386/i686/stack-aliasing.h | 5 ----- 1 file changed, 5 deletions(-) (limited to 'sysdeps/i386/i686/stack-aliasing.h') diff --git a/sysdeps/i386/i686/stack-aliasing.h b/sysdeps/i386/i686/stack-aliasing.h index 7872e47fd4..9b5a1b0d47 100644 --- a/sysdeps/i386/i686/stack-aliasing.h +++ b/sysdeps/i386/i686/stack-aliasing.h @@ -16,11 +16,6 @@ License along with the GNU C Library; if not, see . */ -/* It turns out that stack coloring is in general not good on P4s. Some - applications will benefit. We will probably have a configuration option - at some point. To enable coloring, set this to 128. */ -#define COLORING_INCREMENT 0 - /* What is useful is to avoid the 64k aliasing problem which reliably happens if all stacks use sizes which are a multiple of 64k. Tell the stack allocator to disturb this by allocation one more page if -- cgit 1.4.1