Unreviewed gardening.

Removing redundant pixel and render tree baselines for fast/media tests.
This is the second and last patch covering non-Chromium ports.

Too many files to list.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136718 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Stop generating call stacks inside ContentSecurityPolicy
https://bugs.webkit.org/show_bug.cgi?id=104126

Reviewed by Yury Semikhatsky.

Now that bug 100650 has made it possible for ConsoleMessage to generate
call stacks, we can remove the stack being generated in
ContentSecurityPolicy::logToConsole. We need the ScriptState*, however,
so this patch makes it possible to pipe it through addConsoleMessage
down into the guts of the inspector.

This patch also removes an unused addConsoleMessage variant from
ScriptExecutionContext, which should have been removed from the patch to
100650 before landing it. My bad.

* dom/Document.cpp:
(WebCore::Document::addMessage):
* dom/Document.h:
(Document):
    Accept a ScriptState* parameter in Document::addMessage, and pass it
    through to Console::addMessage.
* dom/ScriptExecutionContext.cpp:
(WebCore::ScriptExecutionContext::addConsoleMessage):
* dom/ScriptExecutionContext.h:
(ScriptExecutionContext):
    Accept a ScriptState* parameter in Document::addMessage, and pass it
    through to ScriptExecutionContext::addMessage. Also, remove an unused
    variant of ScriptExecutionContext::addConsoleMessage that accepted
    only a call stack in addition to the basics.
* inspector/ConsoleMessage.cpp:
(WebCore::ConsoleMessage::ConsoleMessage):
* inspector/ConsoleMessage.h:
(ConsoleMessage):
    Accept a ScriptState* and pass it into autogenerateMetadata for
    call stack generational goodness.
* inspector/InspectorConsoleAgent.cpp:
(WebCore::InspectorConsoleAgent::addMessageToConsole):
    Accept a ScriptState* and pass it into addConsoleMessage.
(WebCore::InspectorConsoleAgent::didFinishXHRLoading):
(WebCore::InspectorConsoleAgent::didReceiveResponse):
(WebCore::InspectorConsoleAgent::didFailLoading):
    Add an empty ScriptState parameter to the addConsoleMessage call.
* inspector/InspectorConsoleAgent.h:
(InspectorConsoleAgent):
* inspector/InspectorConsoleInstrumentation.h:
(WebCore::InspectorInstrumentation::addMessageToConsole):
* inspector/InspectorInstrumentation.cpp:
(WebCore):
(WebCore::InspectorInstrumentation::addMessageToConsoleImpl):
* inspector/InspectorInstrumentation.h:
(InspectorInstrumentation):
* page/Console.cpp:
(WebCore::Console::addMessage):
* page/Console.h:
(Console):
    Pipe ScriptState through the intermediate classes.
* page/ContentSecurityPolicy.cpp:
(WebCore::ContentSecurityPolicy::logToConsole):
    Drop call stack generation, and pass ScriptState* into addConsoleMessage.
* workers/WorkerContext.cpp:
(WebCore::WorkerContext::addConsoleMessage):
(WebCore::WorkerContext::addMessage):
(WebCore::WorkerContext::addMessageToWorkerConsole):
* workers/WorkerContext.h:
(WorkerContext):
    Accept ScriptState* and pass it into addMessageToConsole.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136719 268f45cc-cd09-0410-ab3c-d52691b4dbfc
JSC profiler should not count executions of op_call_put_result because doing so changes DFG codegen
https://bugs.webkit.org/show_bug.cgi?id=104102

Reviewed by Oliver Hunt.

Source/JavaScriptCore: 

This removes op_call_put_result from profiling, since profiling it has an effect on
codegen. This fix enables all of SunSpider, V8, and Kraken to be profiled with the
new profiler.
        
To make this all fit together, the profiler now also reports in its output the exact
bytecode opcode name for each instruction (in addition to the stringified dump of that
bytecode), so that tools that grok the output can take note of op_call_put_result and
work around the fact that it has no counts.

* dfg/DFGByteCodeParser.cpp:
(JSC::DFG::ByteCodeParser::parseBlock):
(JSC::DFG::ByteCodeParser::parseCodeBlock):
* dfg/DFGDriver.cpp:
(JSC::DFG::compile):
* jit/JIT.cpp:
(JSC::JIT::privateCompileMainPass):
* profiler/ProfilerBytecode.cpp:
(JSC::Profiler::Bytecode::toJS):
* profiler/ProfilerBytecode.h:
(JSC::Profiler::Bytecode::Bytecode):
(JSC::Profiler::Bytecode::opcodeID):
(Bytecode):
* profiler/ProfilerDatabase.cpp:
(JSC::Profiler::Database::ensureBytecodesFor):
* runtime/CommonIdentifiers.h:

Tools: 

Modify the profiler to not output counts for op_call_put_result, since there
won't be any. Also fix a few weird bugs, like providing better error reporting
when you type something incorrectly and not reporting counts for slow paths
in the old JIT since those counts are actually not what you think they are
(we don't actually count slow path executions separately).

* Scripts/display-profiler-output:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136720 268f45cc-cd09-0410-ab3c-d52691b4dbfc