https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2020-08-30T15:45:07+00:00 2020-08-30T15:45:07+00:00 mark markm@cs.wisc.edu 2020-08-28T03:58:48+00:00 urn:sha1:9e5f7d5631b8f4009ac1c693e585d4b7108d4275 2020-08-24T11:17:51+00:00 David Wood david@davidtw.co 2020-08-18T10:47:27+00:00 urn:sha1:6cc268e316d37d97fbdda6c1bf3e5a58dea470fe This commit adjusts the naming of various lang items so that they are consistent and don't include prefixes containing the target or "LangItem". In addition, lang item variants are no longer exported from the `lang_items` module. Signed-off-by: David Wood <david@davidtw.co> 2020-08-19T04:06:45+00:00 Rich Kadel richkadel@google.com 2020-08-15T11:42:13+00:00 urn:sha1:d129ac2655451ca894bceeb58a4d5c26a86c4caa 2020-08-18T03:20:27+00:00 Tyler Mandry tmandry@gmail.com 2020-08-18T03:20:27+00:00 urn:sha1:d70ae9bbb79d19c353f00520c6fbaddf00bfde43 Use more compatible out-implib style When calling `rust-lld` directly it accepts only `--out-implib {}` or `--out-implib={}` not `--out-implib,{}`. 2020-08-17T20:32:32+00:00 Ujjwal Sharma ryzokuken@disroot.org 2020-04-27T17:56:11+00:00 urn:sha1:a888b02884883de41d0ce08aa62a6cd6d4790951 2020-08-17T16:40:10+00:00 bors bors@rust-lang.org 2020-08-17T16:40:10+00:00 urn:sha1:8d185cabbdcb1b30ea5f72b3f0b3e6442bc4548a Incorporated Tracing Crate in some libraries Issue #74747 2020-08-16T19:56:36+00:00 Mateusz Mikuła mati865@gmail.com 2020-08-16T19:54:37+00:00 urn:sha1:1627ba19643c18fe9a80e65c8df8bbd2f3ed8432 2020-08-16T18:04:28+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2020-07-14T23:51:46+00:00 urn:sha1:8b86b28f50d7c8fdbbd5f045fe5fefdd314632dc 2020-08-15T11:38:24+00:00 bors bors@rust-lang.org 2020-08-15T11:38:24+00:00 urn:sha1:80fb3f3139c7dee7f211964c6a0b3ccb04b83d5e Add sanitizer support on FreeBSD Restarting #47337. Everything is better now, no more weird llvm problems, well not everything: Unfortunately, the sanitizers don't have proper support for versioned symbols (https://github.com/google/sanitizers/issues/628), so `libc`'s usage of `stat@FBSD_1.0` and so on explodes, e.g. in calling `std::fs::metadata`. Building std (now easy thanks to cargo `-Zbuild-std`) and libc with `freebsd12/13` config via the `LIBC_CI=1` env variable is a good workaround… ``` LIBC_CI=1 RUSTFLAGS="-Z sanitizer=address" cargo +san-test -Zbuild-std run --target x86_64-unknown-freebsd --verbose ``` …*except* std won't build because there's no `st_lspare` in the ino64 version of the struct, so an std patch is required: ```diff --- i/src/libstd/os/freebsd/fs.rs +++ w/src/libstd/os/freebsd/fs.rs @@ -66,8 +66,6 @@ pub trait MetadataExt { fn st_flags(&self) -> u32; #[stable(feature = "metadata_ext2", since = "1.8.0")] fn st_gen(&self) -> u32; - #[stable(feature = "metadata_ext2", since = "1.8.0")] - fn st_lspare(&self) -> u32; } #[stable(feature = "metadata_ext", since = "1.1.0")] @@ -136,7 +134,4 @@ impl MetadataExt for Metadata { fn st_flags(&self) -> u32 { self.as_inner().as_inner().st_flags as u32 } - fn st_lspare(&self) -> u32 { - self.as_inner().as_inner().st_lspare as u32 - } } ``` I guess std could like.. detect that `libc` isn't built for the old ABI, and replace the implementation of `st_lspare` with a panic? 2020-08-15T03:29:12+00:00 pawanbisht62 36775517+pawanbisht62@users.noreply.github.com 2020-08-15T03:29:12+00:00 urn:sha1:bab15885c0ab1230186cc45290c6d6c224289f6b