Add a new API V8::SetJitCodeEventHandler to push code name and location to users such as profilers.

src/builtins.cc

Index: src/builtins.cc
diff --git a/src/builtins.cc b/src/builtins.cc
index 64ec3d9fcc485f9d8fe9c7856072c4f5c4cea84b..4de27854a047450e614840fd8ef8d3ea564b9c7e 100644
--- a/src/builtins.cc
+++ b/src/builtins.cc
@@ -31,7 +31,7 @@
 #include "arguments.h"
 #include "bootstrapper.h"
 #include "builtins.h"
-#include "gdb-jit.h"
+#include "code-events.h"
 #include "ic-inl.h"
 #include "heap-profiler.h"
 #include "mark-compact.h"
@@ -1643,9 +1643,8 @@ void Builtins::SetUp(bool create_heap_objects) {
               CodeCreateEvent(Logger::BUILTIN_TAG,
                               Code::cast(code),
                               functions[i].s_name));
-      GDBJIT(AddCode(GDBJITInterface::BUILTIN,
-                     functions[i].s_name,
-                     Code::cast(code)));
+      JIT_CODE_EVENT(AddCode(functions[i].s_name,

[danno, 2012/07/25 13:50:42]

Why do you remove the code event type? It seems that this even if you don't use
this, it will be useful for other systems, like GDB.

[Sigurður Ásgeirsson, 2012/07/25 14:38:35]

I discussed this with @vegorov at some length, and he feels as I do that these
types don't have much value. I've replaced them with labels based on
code->kind(), which gives you pretty much the same information.

+                             Code::cast(code)));
       builtins_[i] = code;
 #ifdef ENABLE_DISASSEMBLER
       if (FLAG_print_builtin_code) {