about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2020-07-19Only skip impls of foreign unstable traitsMark Rousskov-3/+42
Previously unstable impls were skipped, which meant that any impl with an unstable method would get skipped.
2020-07-19Fix merge conflict with recent PRAlexis Bourget-1289/+3039
2020-07-19Advertise correct stable version for const control flowDylan MacKenzie-2/+2
2020-07-19Clarify core::panic::Location's docs on ordering.Adam Perry-3/+3
Co-authored-by: Simon Sapin <simon.sapin@exyr.org>
2020-07-19tools: update rustfmt toolstate maintainersCaleb Cartwright-1/+1
2020-07-19Teach bootstrap install and dist commands about TargetSelectionJake Goulding-51/+55
With this, we can now use a target JSON file to build a cross-compiler: ``` x.py install --host ../aarch64-apple-darwin.json --target aarch64-apple-darwin ```
2020-07-19Add test for an explicit non-'static lifetime in a const argumentGabriel Smith-0/+28
2020-07-19disallow non-static lifetimes in const genericsGabriel Smith-0/+81
This has been put in place to patch over an ICE caused when we encounter a non-static lifetime in a const generic during borrow checking. This restriction may be relaxed in the future, but we need more discussion before then, and in the meantime we should still deal with this ICE. Fixes issue #60814
2020-07-19Document `core::fmt::rt::v1::Count`Solomon Ucko-0/+4
2020-07-19Document AddressSanitizer memory leak detection defaultsTomasz Miąsko-0/+3
2020-07-19Remove CC & CFLAGS from MemorySanitizer exampleTomasz Miąsko-4/+0
They are now unnecessary for projects written in Rust, since backtrace-rs used by the standard library has only Rust dependencies.
2020-07-19Rewrite extract_version_rangeLzu Tao-23/+46
2020-07-19include backtrace folder in rust-src componentRalf Jung-0/+1
2020-07-19Do not clobber RUSTDOCFLAGSMark Rousskov-6/+11
We were setting these in both Builder::cargo and here, which ended up only setting the first of the two.
2020-07-19Apply suggestions from reviewPoliorcetics-1/+1
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
2020-07-19Auto merge of #74518 - Manishearth:rollup-jfmnh1r, r=Manishearthbors-379/+322
Rollup of 4 pull requests Successful merges: - #74333 (Deny unsafe operations in unsafe functions in libstd/alloc.rs) - #74356 (Remove combine function) - #74419 (Add a thumbv4t-none-eabi target) - #74485 (More intra-doc links, add explicit exception list to linkchecker) Failed merges: - #74486 (Improve Read::read_exact documentation) r? @ghost
2020-07-19Fix panic message when `RangeFrom` index is out of boundsLukas Kalbertodt-3/+9
Before, the `Range` method was called with `end = slice.len()`. Unfortunately, because `Range::index` first checks the order of the indices (start has to be smaller than end), an out of bounds index leads to `core::slice::slice_index_order_fail` being called. This prints the message 'slice index starts at 27 but ends at 10', which is worse than 'index 27 out of range for slice of length 10'. This is not only useful to normal users reading panic messages, but also for people inspecting assembly and being confused by `slice_index_order_fail` calls.
2020-07-19Rollup merge of #74485 - Manishearth:more-intra-doc, r=jyn514Manish Goregaokar-352/+185
More intra-doc links, add explicit exception list to linkchecker Fixes the broken links behind #32553 Progress on #32130 and #32129 except for a small number of links. Instead of whitelisting entire files, I've changed the code to whitelist specific links in specific files, and added a comment requesting people explain the reasons they add exceptions. I'm not sure if we should close those issues in favor of the already filed intra-doc link issues.
2020-07-19Rollup merge of #74419 - Lokathor:gba-target, r=jonas-schievinkManish Goregaokar-0/+63
Add a thumbv4t-none-eabi target (cc @ketsuban, one of the few other Rust users who programs for GBA.) --- **EDIT:** This is now a more general `thumbv4t-none-eabi` PR! See [this comment](https://github.com/rust-lang/rust/pull/74419#issuecomment-660391579) --- Now that the PSP officially has an official target within Rust, well as the lead of the `gba` crate I can't _not_ add a GBA target as well. I know that the [target tier policy](https://github.com/rust-lang/rfcs/pull/2803) isn't ratified and official, but I'll use it as an outline (cc @joshtriplett): * Designated Developer: Lokathor * Naming consistent with any existing targets * Doesn't create Rust project legal issues. * No license issues * Uses the standard Apache/mit license. * Rust tooling users don't have to accept any new licensing requirements * Does not support hosting rust tooling. * Doesn't require linking in proprietary code to obtain a functional binary. However, you will need to do some post-build steps to turn the ELF file into a usable GBA ROM (either for an emulator or for the actual hardware). * This is a `no_std` environment, without even a standard global allocator, so this adds no new code to `alloc` or `std`. * The process of building for this target is documented in the `gba` crate ([link](https://rust-console.github.io/gba/development-setup.html)). Well, the docs there are currently a little out of date, they're back on using `cargo-xbuild`, but the crate docs there will get updated once this target is available. * This places no new burden on any other targets * Does not break any existing targets. I'm not fully confident in specifying the same linker script for all possible projects, so I'm currently just not giving a linker script at all, and users can continue to select their own linker script by using `-C` to provide a linker arg. I added the file, and added it to the `supported_targets!` macro usage, and I think that's all there is to do.
2020-07-19Rollup merge of #74356 - lzutao:rm_combine, r=LukasKalbertodtManish Goregaokar-7/+3
Remove combine function Comparing two array directly helps generate better assert message. Resolve https://github.com/rust-lang/rust/pull/74271/files#r454538514
2020-07-19Rollup merge of #74333 - poliorcetics:std-alloc-unsafe-op-in-unsafe-fn, ↵Manish Goregaokar-20/+71
r=LukasKalbertodt Deny unsafe operations in unsafe functions in libstd/alloc.rs Partial fix of #73904. This encloses `unsafe` operations in `unsafe fn` in `libstd/alloc.rs`. @rustbot modify labels: F-unsafe-block-in-unsafe-fn
2020-07-19Remove useless link to bool primitiveAlexis Bourget-1/+0
2020-07-19do not try fetching the ancestors of errored trait implsBastian Kauschke-1/+19
2020-07-19Rewrite extract_llvm_versionLzu Tao-57/+49
2020-07-19Extract extract_version_rangeLzu Tao-32/+34
2020-07-19Fix small nit in the link to readAlexis Bourget-1/+1
2020-07-19Add missing : after *llvm-versionLzu Tao-7/+7
2020-07-19Auto merge of #74163 - cuviper:debian6, r=Mark-Simulacrumbors-98/+101
ci: Update dist-{i686,x86_64}-linux to Debian 6 This increases the minimum `{i686,x86_64}-unknown-linux-gnu` platform from RHEL/CentOS 5 (glibc 2.5 and kernel 2.6.18) to a slightly newer Debian 6 `squeeze` (glibc 2.11 and kernel 2.6.32). While that release is already EOL, it happens to match the minimum common versions of two enterprise distros that do still need Rust support -- RHEL 6 (glibc 2.12 and kernel 2.6.32) and SLES 11 SP4 (glibc 2.11 and kernel 3.0). Closes #62516.
2020-07-19Add missing : after min-gdb-versionLzu Tao-5/+5
2020-07-19Use subslice patternLzu Tao-6/+6
2020-07-19Extract closure to functionLzu Tao-4/+8
2020-07-19Use Option::as_derefLzu Tao-5/+3
2020-07-19Fix panic as passing wrong format to `extract_gdb_version`Lzu Tao-11/+8
2020-07-19compiletest: Rewrite extract_gdb_version functionLzu Tao-63/+28
2020-07-19compiletest: Rewrite extract_lldb_version functionLzu Tao-76/+50
This makes extract_lldb_version has the same version type like extract_gdb_version. This is technically a breaking change for rustc-dev users. But note that rustc-dev is a nightly component.
2020-07-19Ayu: use different background color to make Run button easy-to-spotLzu Tao-4/+3
Co-authored-by: Cldfire <cldfire@3grid.net>
2020-07-19Auto merge of #74091 - richkadel:llvm-coverage-map-gen-4, r=tmandrybors-262/+1724
Generating the coverage map @tmandry @wesleywiser rustc now generates the coverage map and can support (limited) coverage report generation, at the function level. Example commands to generate a coverage report: ```shell $ BUILD=$HOME/rust/build/x86_64-unknown-linux-gnu $ $BUILD/stage1/bin/rustc -Zinstrument-coverage \ $HOME/rust/src/test/run-make-fulldeps/instrument-coverage/main.rs $ LLVM_PROFILE_FILE="main.profraw" ./main called $ $BUILD/llvm/bin/llvm-profdata merge -sparse main.profraw -o main.profdata $ $BUILD/llvm/bin/llvm-cov show --instr-profile=main.profdata main ``` ![rust coverage report only 20200706](https://user-images.githubusercontent.com/3827298/86697299-1cbe8f80-bfc3-11ea-8955-451b48626991.png) r? @wesleywiser Rust compiler MCP rust-lang/compiler-team#278 Relevant issue: #34701 - Implement support for LLVMs code coverage instrumentation
2020-07-19Fix search input focus in ayu themeJarek Samic-10/+0
2020-07-18primitive impls are weirdManish Goregaokar-1/+1
2020-07-18Clarify the literal stringManish Goregaokar-1/+1
2020-07-18Update src/libstd/io/mod.rsManish Goregaokar-1/+1
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
2020-07-18Update src/tools/linkchecker/main.rsManish Goregaokar-0/+1
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
2020-07-18remove unused importsLokathor-1/+1
2020-07-19Add an border around the Run buttonLzu Tao-0/+1
2020-07-19Auto merge of #74493 - Manishearth:rollup-ust7yr4, r=Manishearthbors-550/+892
Rollup of 7 pull requests Successful merges: - #70817 (Add core::task::ready! macro) - #73762 (Document the trait keyword) - #74021 (impl Index<RangeFrom> for CStr) - #74071 (rustc_metadata: Make crate loading fully speculative) - #74445 (add test for #62878) - #74459 (Make unreachable_unchecked a const fn) - #74478 (Revert "Use an UTF-8 locale for the linker.") Failed merges: r? @ghost
2020-07-18Resolve https://github.com/rust-lang/rust/pull/74419#issuecomment-660518936Lokathor-14/+1
2020-07-18Rollup merge of #74478 - rust-lang:revert-74416-linker-locale-utf8, ↵Manish Goregaokar-3/+1
r=Mark-Simulacrum Revert "Use an UTF-8 locale for the linker." Reverts rust-lang/rust#74416 This is suspected to have caused significant compile time regressions: https://perf.rust-lang.org/compare.html?start=39d5a61f2e4e237123837f5162cc275c2fd7e625&end=d3df8512d2c2afc6d2e7d8b5b951dd7f2ad77b02&stat=instructions:u
2020-07-18Rollup merge of #74459 - canova:const-unreachable-unchecked, r=oli-obkManish Goregaokar-1/+86
Make unreachable_unchecked a const fn This PR makes `std::hint::unreachable_unchecked` a const fn so we can use it inside a const function. r? @RalfJung Fixes #53188.
2020-07-18Rollup merge of #74445 - lcnr:const-generic-ty-decl, r=Dylan-DPCManish Goregaokar-0/+48
add test for #62878 forgot to push this as part of #74159 r? @Dylan-DPC
2020-07-18Rollup merge of #74071 - petrochenkov:cload3, r=matthewjasperManish Goregaokar-543/+474
rustc_metadata: Make crate loading fully speculative Instead of reporting `span_err`s on the spot crate loading errors are now wrapped into the `CrateError` enum and returned, so they are reported only at the top level `resolve_crate` call, and not reported at all if we are resolving speculatively with `maybe_resolve_crate`. As a result we can attempt loading crates for error recovery (e.g. import suggestions) without any risk of producing extra errors. Also, this means better separation between error reporting and actual logic. Fixes https://github.com/rust-lang/rust/issues/55103 Fixes https://github.com/rust-lang/rust/issues/56590
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 22:49:58 +0000