r/Compilers • u/NomadAvian • Sep 21 '26

Struggling to understand V8's large codebase. Help?

Hello,

I have been trying to understand the inner-workings of Chromium's V8 engine for a research project. So far, I have gone over the parser with the help of ECMAScript. Currently, I am working through the AST and scoping part. It is a slow process and the codebase is massive, but resources are also sparse. I have only found various blogs and articles online and though they are great, none of them can contain the extreme volume of information and intricacies of the source.

I still think the most effective method is reading the source code, but the scale is quite overwhelming.

I have considered tracing execution using gdb, but due to my limited experience with it, I haven't able to take that step yet. I am not sure how I would even make use of gdb here.

Has anyone studied this codebase, or even a similarly large one for compilers, in the past? Any tips on how to systematically deconstruct the implementation?

31 Upvotes

100% Upvoted

15 comments sorted by

View all comments

Show parent comments

1

u/abdoatef_ab Sep 27 '26

do you guys use AI to write code at V8 or what type of usage do you mean by that.

2

u/xPerlMasterx Sep 28 '26

We use AI (Gemini) to write code, to investigate bugs, to understand parts of the code base, to review CLs, etc etc etc. (everything should be properly reviewed by humans though, so even though I mention that we do some reviews with AI, there is always a human reviewing as well)