Compilers are an interest of mine so I'll read the article later, but I'm curious whether this is talking about C variety compilers which are generally unsafe, or compilers for managed languages which should never emit code allowing attacks (for some definition of 'never'). Which of these is this article/book discussing?
Hardly that, is about corrupting a state to take control. The CPU just does what it's told (not true, halfway down it starts on Covert channels and side-channels which are a different thing entirely).
On the 1st half, I'm uncertain how it relates to compilers.
Comments
Compilers are an interest of mine so I'll read the article later, but I'm curious whether this is talking about C variety compilers which are generally unsafe, or compilers for managed languages which should never emit code allowing attacks (for some definition of 'never'). Which of these is this article/book discussing?
It's a book (in progress), not an article, and it is talking in large part about compilers for unmanaged languages.
As far as I've understood the article is about how to fool a CPU.
Hardly that, is about corrupting a state to take control. The CPU just does what it's told (not true, halfway down it starts on Covert channels and side-channels which are a different thing entirely).
On the 1st half, I'm uncertain how it relates to compilers.
From skimming a few pages, it seems to be C-family compilers in general.