diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-01-24 12:29:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-24 12:29:51 +0100 |
| commit | 144aeedcf3ec4720c2635bbd20a5b3b1588547e3 (patch) | |
| tree | df469222d15fa329a8bc33eb4dc452e784c0eeca /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | b92a1e9c20327c26097a7ddf55a022d2ea58fbf5 (diff) | |
| parent | 495c7b31aaef783c583d2a0304002367df0a1474 (diff) | |
| download | rust-144aeedcf3ec4720c2635bbd20a5b3b1588547e3.tar.gz rust-144aeedcf3ec4720c2635bbd20a5b3b1588547e3.zip | |
Rollup merge of #93152 - ivmarkov:master, r=m-ou-se
Fix STD compilation for the ESP-IDF target (regression from CVE-2022-21658) Commit https://github.com/rust-lang/rust/commit/54e22eb7dbb615bd44355028d3fd867aa93c0972 broke the compilation of STD for the ESP-IDF embedded "unix-like" Tier 3 target, because the fix for [CVE-2022-21658](https://blog.rust-lang.org/2022/01/20/Rust-1.58.1.html) uses [libc flags](https://github.com/esp-rs/esp-idf-svc/runs/4892221554?check_suite_focus=true) which are not supported on the ESP-IDF platform. This PR simply redirects the ESP-IDF compilation to the "classic" implementation, similar to REDOX. This should be safe because: * Neither of the two filesystems supported by ESP-IDF (spiffs and fatfs) support [symlinks](https://github.com/natevw/fatfs/blob/master/README.md) in the first place * There is no notion of fs permissions at all, as the ESP-IDF is an embedded platform that does not have the notion of users, groups, etc. * Similarly, ESP-IDF has just one "process" - the firmware itself - which contains the user code and the "OS" fused together and running with all permissions
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
