> You could add a check to configure and generate based on that? Do you mean check if glibc is newer than 2.13? I think that when new glibc version is released, the tables should be re-examined anyway - we shouldn't just stop inlining, or stop generating libcalls.
> BTW I know that the tables need tuning for Nehalem and Sandy Bridge too. > Michael are you planning to do that? There is no separate cost-table for Nehalem or SandyBridge - however, I tuned generic32 and generic64 tables, that should improve performance on modern processors. In old version REP-MOV was used - it turns out to be slower than SSE-moves or libcalls (in my version the fastest from these options is used).
