We shouldn't re-implement memcmp
We shouldn't re-implement memcmp

There's no reason to re-implement memcmp in WTF::equal. These
architecture-specific implementations were introduced in
http://trac.webkit.org/changeset/101747, where they were a speedup over a naive
loop. However, a better point of comparison is memcmp, which compilers are good
at optimizing.

To evaluate this change, I compared the previous x86_64-specific implementation
with memcmp on Linux using gcc with our current compiler options. I found that
memcmp was 3.8% faster (average of five runs).  I didn't do a full statistical
analysis, but there doesn't seem to be any reason to keep these hand-rolled
memcmp implementations.

R=jochen,eseidel

Review URL: https://chromiumcodereview.appspot.com/18982002

git-svn-id: bf5cd6ccde378db821296732a091cfbcf5285fbd@153870 bbb929c8-8fbe-4397-9dbb-9b2b20218538

axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk