5 ms·

This particular attack is done entirely in the rustc frontend, so adding another way to build the backend shouldn't matter? One requires a new implementation of

by Gankro 10y ago

This particular attack is done entirely in the rustc frontend, so adding another way to build the backend shouldn't matter? One requires a new implementation of the frontend to apply diversity mitigations.

kibwen 10y ago
Which makes me wonder if Miri ( https://github.com/solson/miri https://github.com/solson/miri ) counts as an alternate implementation of the frontend. Combined with, say, Cretonne ( https://internals.rust-lang.org/t/possible-alternative-compiler-backend-cretonne/4275 https://internals.rust-lang.org/t/possible-alternative-compi... ) I wonder if we couldn't cobble together an alternate frankencompiler for mitigating RoTT.
- Manishearth 10y ago
  You need to generate the MIR though (to feed to miri); this only fixes attacks that happen in the pipeline after MIR. Doing path and type resolution is the tough part and so far we only have one implementation of that. https://github.com/thepowersgang/mrustc https://github.com/thepowersgang/mrustc exists, anyway. I don't think it can compile rustc yet.
- deleted 10y ago
  [deleted]