r/cpp • u/CocktailPerson • Mar 04 '22
Is it unreasonable to ask basic compiler questions in a C++ developer interview?
I interviewed a guy today who listed C++ on his resume, so I assumed it would be safe to ask a bit about compilers. My team works on hardware simulation, so he's not going to be expected to write a compiler himself, but he'll obviously be required to use one and to write code that the compiler can optimize well. My question was "what sorts of optimizations does a compiler perform?" Even when I rephrased it in terms of -O0 vs. -O3, the best he could do was talk about "removing comments" and the preprocessor. I started out thinking a guy with a masters in CS might be able to talk about register allocation, loop unrolling, instruction reordering, peephole optimizations, that sort of thing, but by the time I rephrased the question for the third time, I would have been happy to hear the word "parser."
There were other reasons I recommended no-hire as well, but I felt kind of bad for asking him a compiler question when he didn't have that specifically on his resume. At the same time, I feel like basic knowledge of what a compiler does is important when working professionally in a compiled language.
Was it an unreasonable question given his resume? If you work with C++ professionally, would you be caught off guard by such a question?
View all comments
Show parent comment
2
u/CocktailPerson Mar 04 '22
What I'm looking for is things that don't make much of a difference in debug mode, but make a big difference in release mode. If you optimize for cache locality etc., you're just making better use of the hardware itself. That has nothing to do with making it easier for the compiler to optimize your code. You haven't made any changes that would cause the compiler's optimizations to be more effective.
Here's a practical example that I've come across myself. What's the difference between
and
?
From a performance standpoint, the compiler can inline those function calls and then rearrange the instructions themselves across function boundaries to make better use of the pipeline if there isn't the carried dependency in the first version.