{"id":25648,"date":"2020-03-13T01:15:17","date_gmt":"2020-03-13T01:15:17","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=25648"},"modified":"2020-03-16T19:38:42","modified_gmt":"2020-03-16T19:38:42","slug":"more-spectre-mitigations-in-msvc","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/more-spectre-mitigations-in-msvc\/","title":{"rendered":"More Spectre Mitigations in MSVC"},"content":{"rendered":"

In a previous blog post, Microsoft described the Spectre mitigations <\/a>available under \/Qspectre<\/code>. These mitigations, while not significantly impacting performance, do not protect against all possible speculative load attacks, described in industry research as Load Value Injection<\/a>. We are now adding two new switches \/Qspectre-load<\/code> and \/Qspectre-load-cf<\/code> to provide a more complete mitigation of Spectre attacks<\/a> based on loads for customers. These switches are only available on x86 and x64 platforms.<\/p>\n

What do the new switches do?<\/h2>\n

The \/Qspectre-load<\/code> flag<\/a> specifies compiler generation of serializing instructions for every load instruction. For most loads, this entails adding an LFENCE<\/code> instruction after the load instruction. However, for control flow instructions, this approach does not work. In most cases, the instruction can be split into the load and control flow, so an LFENCE<\/code> can be inserted after the load. When this is not possible, such as for jmp [rax]<\/code> the compiler uses an alternate mitigation strategy, loading the target non-destructively before inserting an LFENCE<\/code> as follows:<\/p>\n

xor rbx, [rax]\r\nxor rbx, [rax] \r\nlfence\r\njmp [rax]<\/pre>\n
The \/Qspectre-load-cf<\/code> flag<\/a> provides a subset of this behavior, only protecting control flow instructions: JMP<\/code>, RET<\/code>, and CALL<\/code>.<\/p>\n
If there are performance critical blocks of code that do not require protection, then you can disable these mitigations using __declspec(spectre(nomitigation))<\/code>. As these switches stop speculation of all loads, the performance impact is very high, so this mitigation is not appropriate everywhere.<\/p>\n
What versions of MSVC support the \/Qspectre-load and \/Qspectre-load-cf switches?<\/h2>\n
These switches are available starting in Visual Studio 16.5 preview 3 and will be available in MSVC toolsets included in all future releases of Visual Studio (including Previews). They have also been released in all currently supported versions of Visual Studio 2017 and 2019 as follows:<\/p>\n