On 1/5/18, Eric Gallager <eg...@gwmail.gwu.edu> wrote: > On 1/4/18, Will Hawkins <wh...@virginia.edu> wrote: >> On Thu, Jan 4, 2018 at 10:10 PM, Eric Gallager <eg...@gwmail.gwu.edu> >> wrote: >>> Is there anything GCC could be doing at the compiler level to mitigate >>> the recently-announced Meltdown and Spectre vulnerabilities? From >>> reading about them, it seems like they involve speculative execution >>> and indirect branch prediction, and those are the domain of things the >>> compiler deals with, right? (For reference, Meltdown is CVE-2017-5754, >>> and Spectre is CVE-2017-5753 and CVE-2017-5715) >>> >>> Just wondering, >>> Eric >> >> Check out >> >> https://support.google.com/faqs/answer/7625886 >> >> and especially >> >> http://git.infradead.org/users/dwmw2/gcc-retpoline.git/shortlog/refs/heads/gcc-7_2_0-retpoline-20171219 >> >> I'd love to hear what other people have heard! >> >> Will >> > > Thanks, this is what I was looking for. Seeing commits by H.J. Lu in > that branch gives me confidence that it'll eventually make it back > into trunk. > > Eric >
Oh, and apparently there was already a thread on gcc-patches relevant to this as of yesterday that I missed; it's here: https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00205.html ("[PATCH 0/3] Add __builtin_load_no_speculate")
