silwol

For the record, the Debian package got uploaded some time ago with a description of the [copyright situation explained](https://salsa.debian.org/rust-team/debcargo-conf/blob/8c273d606c1ced81d0753b7706e51bda28a21073/src/compiler-builtins/debian/copyright), and now was [rejected](https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2020-February/009954.html) by our FTP-Masters team again.

I took a look at the LICENSE.TXT file, and it includes hints to the CREDITS.TXT file, which is not present in this project, but in compiler-rt. Even if the license...

Is there anything we as debian-rust can do to support progress here? This is one of a few serious issues that have stalled the packaging efforts of Rust crates inside...

Of course it's ok for me. Thank you!

If we strive to follow the [API guidelines](https://rust-lang.github.io/api-guidelines/interoperability.html), I think it makes sense to rather expose a `deserialize_unchecked(…)` method that may panic, and a `deserialize(…)` method that does checking and...

The proposed C API looks sane to me, it's the equivalent to what we already provide for `stdout` and `stderr`, just the reverse direction (`write` vs. `read`).

I'd prefer to have the tests published as well. Rationale: in Debian we run the tests in the form of autopkgtests as a verification that our package contents build fine...

> Thank you for the very detailed report! I have a feeling that this will end up being a compiler issue, either in rustc or LLVM, since there's nothing arch-specific...

I explored a bit further, and it seems that the doc example doesn't even call the `FloatCore` implementation of the `min` and `max` methods. Even when simply putting a `unimplemented!()`...

Maybe it's a manifestation of https://github.com/rust-lang/rust/issues/52746? It's reproducible with plain usage of std. This piece of code succeeds on my amd64 box while failing on the mipsel vm. ```rust #[cfg(test)]...