Compiler Design - Daniel Alillo

I’ve always been curious about how programming has evolved into what we know today, from zeros and ones to an actual language. So, I was immensely surprised when I discovered how much was accomplished by a single person: Grace Hopper. Her entire life is admirable in so many different ways. Being a woman who wanted to study math and science should’ve been very hard, let alone being in the navy in a high position, however she was able to fight against all odds and even got the honor of being an admiral. That said, though her fight against all women prejudices is an outstanding feat, her contributions to programming languages are what made me go from respecting her to truly admire her. She wasn’t afraid that proposing such a weird idea as writing programs using human language would make her a victim of skeptical opinions. She wanted everyone was able to write programs without needing deep knowledge in math. She knew there was a lot of potential for the new generations to create some

It’s funny, I’ve been using gcc for like two years and there’s still hundreds of things I completely ignore about it. I wasn’t fully aware of what it did let alone how. That’s why I really found interesting this podcast, as we delve into the processes that are being carried out in order to make a set of consecutive cone lines into actual commands that the computer is able to interpret. There are three different parts that make a compiler which include: a front end, an intermediate and a back end. Each of them is separate from one another and yet the communication among them is vital for the process of compilation. This allows the programs to be portable and not hardware dependent. Also, this gives more freedom to develop different PC architectures without worrying about compatibility. At the beginning of the podcast, the invited one makes an interesting observation where he states that knowing the inner processes that take place inside a compiler might not be necessary but can be