Hi Luc, Per our discussion, here is some test you are interested. It show some measurable difference in ptrlist-iterator vs the base before the patch series. Step to reproduce: git clone git://source.winehq.org/git/wine.git cd win/dlls/usp10/tests The test command: time sparse -m64 -c -o usp10.o usp10.c -I. -I../../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -g -O2 I run the test on ptrlist-iterator from the git url you send out. Here is 3 runs each on ptrlist-iterator and the base line commit. with ptrlist-iterator d55cac721a060882df02f40aab8824d210d9dc6f real 0m25.764s user 0m25.430s sys 0m0.227s real 0m25.746s user 0m25.424s sys 0m0.219s real 0m25.800s user 0m25.326s sys 0m0.201s with base(rc4) ec3f72e981792a86a9e002471a06d61ecd5c6675 real 0m23.625s user 0m23.311s sys 0m0.190s real 0m23.489s user 0m23.002s sys 0m0.195s real 0m23.321s user 0m23.043s sys 0m0.185s Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
