Ah, looks like we can follow existing map transitions without entering
ic.cc code.
Adding --nolazy-feedback-allocation should disable that.
On Fri, Nov 11, 2022 at 9:02 PM Filip Petronijevic <
fpetronijevic661...@raf.rs> wrote:
> Thank you for the reply. I have one very weird problem (not sure
Thank you for the reply. I have one very weird problem (not sure if its a
bug).
I ran Chromium with arguments you told me and args.gn setup and when I run
this code
var obj143 = {};
obj143["test"] = {test: 1, test2: 2, test3: 3};
var obj221 = {};
obj221["test"] = {test3: 14, test5: 23, test6:
On Fri, Nov 11, 2022 at 1:15 PM Filip Petronijevic <
fpetronijevic661...@raf.rs> wrote:
> I treced down 'job' macro from tools/gdbinit and I found out it calls in
> the end
>
I treced down 'job' macro from tools/gdbinit and I found out it calls in
the end
https://source.chromium.org/chromium/chromium/src/+/main:v8/src/objects/objects.h;drc=a0dedabb214a245c792009e64baf333c7e8d7357;l=679
which is shortPrint. This still doesn't show me all level depths of an
object but
>
> Thanks! I found this StoreIC::Store() function just yesterday while
> debugging in D8 and it works even without (--nouse-ic flag), even though I
> have no clue what this flag does as I can't find it in docs. But this
> tracks all of the keys and objects created.
No, it won't catch all of
Thanks! I found this StoreIC::Store() function just yesterday while
debugging in D8 and it works even without (--nouse-ic flag), even though I
have no clue what this flag does as I can't find it in docs. But this
tracks all of the keys and objects created.
The main problem now is the
Maps don't keep lists of the objects that use them. To find all objects
that use a given map, you'd have to walk the entire heap to find all
objects, and filter them by map.
Considering your previous question, I'm not sure finding all objects that
use a given map will actually be helpful. A
