https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.41.0 2020-01-13T21:19:11+00:00 2020-01-13T21:19:11+00:00 Jeremy Fitzhardinge jeremy@goop.org 2019-12-11T07:32:52+00:00 urn:sha1:50132c4ae36fe6fb0124c44700ce0cb576bf7e15 PR https://github.com/rust-lang/rust/pull/66512 added the ability to set argv[0] on Command. As a side effect, it changed the Debug output to print both the program and argv[0], which in practice results in stuttery output ("echo echo foo"). This PR reverts the behaviour to the the old one, so that the command is only printed once - unless arg0 has been set. In that case it emits "[command] arg0 arg1 ...". 2019-12-15T04:57:22+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-12-15T04:57:22+00:00 urn:sha1:39c5d8199aa5cf049585a3a458c590c6a4d4a6ca Fix signature of `__wasilibc_find_relpath` Looks like this function changed upstream, so it needs to be adjusted for when used by libstd. 2019-12-14T04:08:50+00:00 bors bors@rust-lang.org 2019-12-14T04:08:50+00:00 urn:sha1:12307b3b08edee543a78fb9d4a837fbd6d6ac0fa SGX: Change ELF entrypoint This fixes [rust-sgx issue #148](https://github.com/fortanix/rust-sgx/issues/148). A new entry point is created for the ELF file generated by `rustc`, separate from the enclave entry point. When the ELF file is executed as a Linux binary, the error message below is written to stderr. > Error: This file is an SGX enclave which cannot be executed as a standard Linux binary. > See the installation guide at https://edp.fortanix.com/docs/installation/guide/ on how to use 'cargo run' or follow the steps at https://edp.fortanix.com/docs/tasks/deployment/ for manual deployment. When the ELF file is converted to an SGXS using `elf2sgxs`, the old entry point is still set as the enclave entry point. In a future pull request in the rust-sgx repository, `elf2sgxs` will be modified to remove the code in the ELF entry point, since this code is not needed in the enclave. 2019-12-12T22:48:47+00:00 Alex Crichton alex@alexcrichton.com 2019-12-12T22:48:47+00:00 urn:sha1:641ccd58c168a296f5c36a191660ef63a32a98b9 Looks like this function changed upstream, so it needs to be adjusted for when used by libstd. 2019-12-11T16:00:37+00:00 chansuke chansuke@georepublic.de 2019-12-11T16:00:37+00:00 urn:sha1:e4852da576bda4a5d26341961e0be7d6626ff5c0 2019-12-09T10:39:57+00:00 Lzu Tao taolzu@gmail.com 2019-12-09T10:39:57+00:00 urn:sha1:bf1f1c242c084e6d74677e228db9d5d6595af7af 2019-12-06T09:54:53+00:00 Pieter Agten pieter.agten@fortanix.com 2019-12-06T09:54:53+00:00 urn:sha1:f02ffb8b4ca760117875f3b5326e9cff6598dde3 2019-12-06T07:43:56+00:00 bors bors@rust-lang.org 2019-12-06T07:43:56+00:00 urn:sha1:d0126e8ed3cc0d6fcb9dd44c36a46f9ce65010a0 Rollup of 10 pull requests Successful merges: - #66649 (VxWorks: fix issues in accessing environment variables) - #66764 (Tweak wording of `collect()` on bad target type) - #66900 (Clean up error codes) - #66974 ([CI] fix the `! isCI` check in src/ci/run.sh) - #66979 (Add long error for E0631 and update ui tests.) - #67017 (cleanup long error explanations) - #67021 (Fix docs for formatting delegations) - #67041 (add ExitStatusExt into prelude) - #67065 (Fix fetching arguments on the wasm32-wasi target) - #67066 (Update the revision of wasi-libc used in wasm32-wasi) Failed merges: r? @ghost 2019-12-06T06:37:13+00:00 Yuki Okushi huyuumi.dev@gmail.com 2019-12-06T06:37:13+00:00 urn:sha1:f77b8d355bca91587ea5370c9294f71052dca977 Fix fetching arguments on the wasm32-wasi target Fixes an error introduced in #66750 where wasi executables always think they have zero arguments because one of the vectors returned here accidentally thought it was length 0. 2019-12-06T06:37:11+00:00 Yuki Okushi huyuumi.dev@gmail.com 2019-12-06T06:37:11+00:00 urn:sha1:1bb868c5d63a2f73f70558075781b9c49e76c860 add ExitStatusExt into prelude r? @alexcrichton