Re: [go-nuts] retpolines in the go compiler?

On Thu, Jan 4, 2018 at 9:41 AM, wrote: > > The last few days have seen some scary CPU security issues. One is Spectre, > which takes advantage of branch prediction and cache timings to read memory > that should be inaccessible. > > The main (only?) mitigation that I have

[go-nuts] retpolines in the go compiler?

The last few days have seen some scary CPU security issues. One is Spectre , which takes advantage of branch prediction and cache timings to read memory that should be inaccessible. The main (only?) mitigation that I have seen is to use "retpolines" - a portmanteau