On Jan 16, 2012, at 08:21, Kerry wrote: > > Performance is one of the strongest reasons for coding in assembler and > this discussion characterizes some of the low hanging fruit available for > the attainment thereof. > Others have said here that performance is a strong reason for _not_ coding in assembler:
o Compiler developers have done the research on instruction timings and know better than most end users what sequences fit the pipelines optimally. o Compiled code can be re-optimized for a new generation of hardware simply by recompiling. o Interpreters can dynamically recompile based on statistical profiles evaluated at the actual time of execution. -- gil
