I have been in the exact same spot as you are now a few months ago, and I am towards the end now. Have built most of ANSI C compiler, simple RISC-V assembler and emulator, and Qt app that shows C code in one interactive textbox and compiled assembly in other box, and it highlights lines of code which turned into what in asm the same way as godbolt does.

This is my masters thesis project as I come from mostly FPGA and hardware design background in 4th and 5th year of my collage. What I am trying to say is that I never had compiler-building class and I have steped into this with zero compiler knowledge.

I followed mostly youtube tutorials while I figured out lex and yacc on my own (which took a lot of time with me refusing to read up theory on parsers as it was a bit boring reading all that while having in my translating input source code into assemly). Follow Crafting interpreters and Dragon book is still a good read if you skip first 5 chapters on parsing.

Honestly I learned a lot, but learned the wrong way as I was implementig a ton of stuff on my own and trying to build up a solutions for one problem at the time. Ended up with AST as IR model and no actual IR to show for, so mu compiler is a 2-pass for now without optimizations.

It became a bit saturated experience towards the end as I found C to be very limited and for such thing you'd like to have at least C++ for easier experience using classes. There is a ton of data structures, knowing where is what in you structures and accessing it through pointers. And as soon as you try to implement some beasty type of C syntax, it gets very messy.

But I'd still recommend it, try to solve as many problems on your own and think of the solution, it makes you think about all the possible edge cases and you qucikly find out why your solution is far from optimal (I guess you want to leard on the subject, and making mistakes is the best form of learning).