A few MallocBench record/replay fixes
authorggaren@apple.com <ggaren@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Mon, 14 Apr 2014 19:11:50 +0000 (19:11 +0000)
committerggaren@apple.com <ggaren@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Mon, 14 Apr 2014 19:11:50 +0000 (19:11 +0000)
commit7901101d7cbe697eb2e7a4165fc30829ca8934c0
treeaf215b56c3603575f92b683497504cb969b36969
parent92df37c6322b93d3cf854cbbb82c4a455673ab46
A few MallocBench record/replay fixes
https://bugs.webkit.org/show_bug.cgi?id=131627

Reviewed by Andreas Kling.

* MallocBench/MallocBench/Interpreter.cpp:
(Interpreter::run): Accept 0-sized allocations without asserting because
WebKit does that sometimes.

* MallocBench/MallocBench/flickr.ops:
* MallocBench/MallocBench/flickr_memory_warning.ops:
* MallocBench/MallocBench/reddit.ops:
* MallocBench/MallocBench/reddit_memory_warning.ops:
* MallocBench/MallocBench/theverge.ops:
* MallocBench/MallocBench/theverge_memory_warning.ops: Updated these
recordings because a bug in the recording mechanism caused one out of
every few thousand slot values to be bogus.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@167260 268f45cc-cd09-0410-ab3c-d52691b4dbfc
PerformanceTests/ChangeLog
PerformanceTests/MallocBench/MallocBench/Interpreter.cpp
PerformanceTests/MallocBench/MallocBench/flickr.ops
PerformanceTests/MallocBench/MallocBench/flickr_memory_warning.ops
PerformanceTests/MallocBench/MallocBench/reddit.ops
PerformanceTests/MallocBench/MallocBench/reddit_memory_warning.ops
PerformanceTests/MallocBench/MallocBench/theverge.ops
PerformanceTests/MallocBench/MallocBench/theverge_memory_warning.ops