aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAdrian Bunk <bunk@stusta.de>2006-03-08 02:58:36 -0500
committerSam Ravnborg <sam@mars.ravnborg.org>2006-03-12 17:35:17 -0500
commit8cab77a2f851363e35089b9720373b964f64550e (patch)
treefdb88e137cc2a1b6a62fd92eeae6d35f3c882b3e
parent7d1859835cd6c0afd1773d249300da82b1b868a5 (diff)
Kconfig: remove the CONFIG_CC_ALIGN_* options
I don't see any use case for the CONFIG_CC_ALIGN_* options: - they are only available if EMBEDDED - people using EMBEDDED will most likely also enable CC_OPTIMIZE_FOR_SIZE - the default for -Os is to disable alignment In case someone is doing performance comparisons and discovers that the default settings gcc chooses aren't good, the only sane thing is to discuss whether it makes sense to change this, not through offering options to change this locally. Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
-rw-r--r--Makefile7
-rw-r--r--init/Kconfig37
2 files changed, 0 insertions, 44 deletions
diff --git a/Makefile b/Makefile
index eca667b4098e..3dbaac6d521d 100644
--- a/Makefile
+++ b/Makefile
@@ -472,13 +472,6 @@ else
472CFLAGS += -O2 472CFLAGS += -O2
473endif 473endif
474 474
475#Add align options if CONFIG_CC_* is not equal to 0
476add-align = $(if $(filter-out 0,$($(1))),$(cc-option-align)$(2)=$($(1)))
477CFLAGS += $(call add-align,CONFIG_CC_ALIGN_FUNCTIONS,-functions)
478CFLAGS += $(call add-align,CONFIG_CC_ALIGN_LABELS,-labels)
479CFLAGS += $(call add-align,CONFIG_CC_ALIGN_LOOPS,-loops)
480CFLAGS += $(call add-align,CONFIG_CC_ALIGN_JUMPS,-jumps)
481
482ifdef CONFIG_FRAME_POINTER 475ifdef CONFIG_FRAME_POINTER
483CFLAGS += -fno-omit-frame-pointer $(call cc-option,-fno-optimize-sibling-calls,) 476CFLAGS += -fno-omit-frame-pointer $(call cc-option,-fno-optimize-sibling-calls,)
484else 477else
diff --git a/init/Kconfig b/init/Kconfig
index 38416a199def..411600cac88c 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -354,43 +354,6 @@ config SHMEM
354 option replaces shmem and tmpfs with the much simpler ramfs code, 354 option replaces shmem and tmpfs with the much simpler ramfs code,
355 which may be appropriate on small systems without swap. 355 which may be appropriate on small systems without swap.
356 356
357config CC_ALIGN_FUNCTIONS
358 int "Function alignment" if EMBEDDED
359 default 0
360 help
361 Align the start of functions to the next power-of-two greater than n,
362 skipping up to n bytes. For instance, 32 aligns functions
363 to the next 32-byte boundary, but 24 would align to the next
364 32-byte boundary only if this can be done by skipping 23 bytes or less.
365 Zero means use compiler's default.
366
367config CC_ALIGN_LABELS
368 int "Label alignment" if EMBEDDED
369 default 0
370 help
371 Align all branch targets to a power-of-two boundary, skipping
372 up to n bytes like ALIGN_FUNCTIONS. This option can easily
373 make code slower, because it must insert dummy operations for
374 when the branch target is reached in the usual flow of the code.
375 Zero means use compiler's default.
376
377config CC_ALIGN_LOOPS
378 int "Loop alignment" if EMBEDDED
379 default 0
380 help
381 Align loops to a power-of-two boundary, skipping up to n bytes.
382 Zero means use compiler's default.
383
384config CC_ALIGN_JUMPS
385 int "Jump alignment" if EMBEDDED
386 default 0
387 help
388 Align branch targets to a power-of-two boundary, for branch
389 targets where the targets can only be reached by jumping,
390 skipping up to n bytes like ALIGN_FUNCTIONS. In this case,
391 no dummy operations need be executed.
392 Zero means use compiler's default.
393
394config SLAB 357config SLAB
395 default y 358 default y
396 bool "Use full SLAB allocator" if EMBEDDED 359 bool "Use full SLAB allocator" if EMBEDDED