It would be cool if people doing this kept a journal, and wrote down changes in the way they think and feel during this. I tried it twice, and lasted a solid two weeks during one of the attempts, but it wreaked havoc on my ability to store and/or recall memories. I would have a lot of trouble telling you what I did a few days ago, and I would be irrationally angry/upset for about 15 seconds at the person who woke me up.(I did this with a group of three.) A few times I yelled angry nonsense at them for this short time. We had a "safe word" that was supposed to prove we were awake, ours was "alligator". After one nap I was woken up, angrily hissed "ARMADILLO" and tried to go back to sleep. It was pretty funny even at the time, but I decided to stop since I figured it wasn't good for me, and I was pretty miserable. I was definitely micro sleeping at times as well, so I'll echo Petruchio's warning about looking out for that.

Best of luck, hope it works out for you better than it did for me.

If you're seriously considering Glasgow, tell them you have a better offer and they need to beat it.

I haven't studied the field in awhile, but back when I did, I got a lot from Advanced Compiler Design & Implementation by Steven Muchnick.

There is an unfortunate tendency, when teaching about compilers, to teach about components in the order they would be built in a project course, which puts a lot of undue emphasis on the boring solved problem of parsing. The layman's view of a compiler is that it translates from high-level languages to machine code; the reality is that it translates from a high-level language through a series of intermediate representations, each of which brings out some property that makes it amenable to optimizations; and these optimizations and representations are what make up the bulk of a compiler. A good litmus-test for understanding, is ability to translate a function into static single assignment (SSA) form.