deps: remove problematic comment from v8-internal

GCC emits warnings because of the trailing backslashes.

PR-URL: #58070
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
PR-URL: #58064
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Paolo Insogna <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>

Author: targos

common.gypi

@@ -38,7 +38,7 @@
 
     # Reset this number to 0 on major V8 upgrades.
     # Increment by one for each non-official patch applied to deps/v8.
-    'v8_embedder_string': '-node.3',
+    'v8_embedder_string': '-node.4',
 
     ##### V8 defaults for Node.js #####
 

deps/v8/include/v8-internal.h

@@ -423,19 +423,6 @@ constexpr size_t kMaxCppHeapPointers = 0;
 // which all subtypes of a given supertype use contiguous tags. This struct can
 // then be used to represent such a type range.
 //
-// As an example, consider the following type hierarchy:
-//
-//          A     F
-//         / \
-//        B   E
-//       / \
-//      C   D
-//
-// A potential type id assignment for range-based type checks is
-// {A: 0, B: 1, C: 2, D: 3, E: 4, F: 5}. With that, the type check for type A
-// would check for the range [A, E], while the check for B would check range
-// [B, D], and for F it would simply check [F, F].
-//
 // In addition, there is an option for performance tweaks: if the size of the
 // type range corresponding to a supertype is a power of two and starts at a
 // power of two (e.g. [0x100, 0x13f]), then the compiler can often optimize