Creating this issue to discuss #63597. @Sergey Togi Dashnyam -- feel free to ask some questions here :)
Though I'll try to leave a few more notes about what's expected in the issue itself
One thing you can do btw is ask the triagebot to assign you; I think it's
Ok, I'm currently reading linked issues
as I have no context atm
Let me read the entire history and
I'll restate what my understanding of this issue is
Rust's Target feature leads to segfaults.
1. Rust has a Target feature for different CPU architectures. Binaries for e.g. ARM, x86 architectures differ, since they have different CPU instruction sets.
2. Using the target feature is atm unsafe, because
floats are compiled to soft-floats (software emulated floats)
-- OR --
native floats (used via ABIs --> goes to Floating Processing Unit)
mixed usage leads to segfault (trying to access reserved memory).
using crates will result in mixed usage, too
There is no quick solution, but documenting stuff is always good.
FILES TO MODIFY: (... will come in next posting)
The docfiles to modify are:
@nikomatsakis where do I find the -Chelp files?
@Sergey Togi Dashnyam heh I'm not sure -- there's some macro somewhere
ah, here it is
it looks like
--print target-features winds up somewhere around this code
Thanks, will do a draft PR on the weekend.
@nikomatsakis I created a PR https://github.com/rust-lang/rust/pull/64145
@Sergey Togi Dashnyam awesome! :heart_eyes: