mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7e143e9043
rust/compiler/rustc_symbol_mangling/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

24 lines
618 B
TOML
Raw Normal View History

mv compiler to compiler/
2020-08-27 22:58:48 -05:00
[package]
name = "rustc_symbol_mangling"
version = "0.0.0"
Migrate to 2021
2021-09-19 11:49:55 -05:00
edition = "2021"
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
[lib]
[dependencies]
Add fine-grained LLVM CFI support to the Rust compiler This commit improves the LLVM Control Flow Integrity (CFI) support in the Rust compiler by providing forward-edge control flow protection for Rust-compiled code only by aggregating function pointers in groups identified by their return and parameter types. Forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space) will be provided in later work as part of this project by identifying C char and integer type uses at the time types are encoded (see Type metadata in the design document in the tracking issue #89653). LLVM CFI can be enabled with -Zsanitizer=cfi and requires LTO (i.e., -Clto).
2022-04-01 00:50:41 -05:00
bitflags = "1.2.1"
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
tracing = "0.1"
punycode = "0.4.0"
Update rustc-demangle to 0.1.21.
2021-08-10 16:05:25 -05:00
rustc-demangle = "0.1.21"
Add LLVM KCFI support to the Rust compiler This commit adds LLVM Kernel Control Flow Integrity (KCFI) support to the Rust compiler. It initially provides forward-edge control flow protection for operating systems kernels for Rust-compiled code only by aggregating function pointers in groups identified by their return and parameter types. (See llvm/llvm-project@cff5bef.) Forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space) will be provided in later work as part of this project by identifying C char and integer type uses at the time types are encoded (see Type metadata in the design document in the tracking issue #89653). LLVM KCFI can be enabled with -Zsanitizer=kcfi. Co-authored-by: bjorn3 <17426603+bjorn3@users.noreply.github.com>
2022-11-21 23:29:00 -06:00
twox-hash = "1.6.3"
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_span = { path = "../rustc_span" }
rustc_middle = { path = "../rustc_middle" }
rustc_hir = { path = "../rustc_hir" }
Add `rustc_fluent_macro` to decouple fluent from `rustc_macros` Fluent, with all the icu4x it brings in, takes quite some time to compile. `fluent_messages!` is only needed in further downstream rustc crates, but is blocking more upstream crates like `rustc_index`. By splitting it out, we allow `rustc_macros` to be compiled earlier, which speeds up `x check compiler` by about 5 seconds (and even more after the needless dependency on `serde_json` is removed from `rustc_data_structures`).
2023-04-16 07:33:00 -05:00
rustc_fluent_macro = { path = "../rustc_fluent_macro" }
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_target = { path = "../rustc_target" }
rustc_data_structures = { path = "../rustc_data_structures" }
rustc_session = { path = "../rustc_session" }
ADD - InvalidSymbolName to migrate symbol-name({}) error to new diagnostics infraestructure ADD - dependencies needed to port a module to new Diagnostics infra (rustc_macros, rustc_errors, errors file, and fluent file)
2022-08-26 23:24:13 -05:00
rustc_macros = { path = "../rustc_macros" }
rustc_errors = { path = "../rustc_errors" }
Reference in New Issue Copy Permalink