Nathan Sidwell wrote:
Steven Munroe wrote:
add the --with-cpu support as a way to manage this. You all might be
very annoyed with me, if I had 970/power4/power5/power5+/power6/power6x
specific code cluttering up performance sensitive common code!
This patch is not cluttering up performance sensitive common code.
memset already has a check for whether the cache line size is zero.
Please don't construct straw men :)
Memset is performance sensitive code and the dynamic __cache_line_size
check is slowing down 970/power4/power5/power5+/power6/power6x. When the
processor can retire (up to) 5 instructions per cycle, the dependent
sequence to address the GOT and check the __cache_line_size is very
noticable.