summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2023-05-29Use the standard macOS CI runnerRyan Levick-1/+1
2023-05-29Prepare 1.70.0 releaseMark Rousskov-1/+1
2023-05-06bootstrap: add .gitmodules to the sourcesKrasimir Georgiev-0/+1
The bootstrap builder now expects this file to exist: https://github.com/rust-lang/rust/blob/6f8c0557e0b73c73a8a7163a15f4a5a3feca7d5c/src/bootstrap/builder.rs#L494
2023-05-04[beta] Update cargoWeihang Lo-0/+0
2023-04-28Update awscliEric Huss-3/+4
(cherry picked from commit dd6314f96cbe9057572dfd8b49e31e113eebe42f)
2023-04-26Bump bootstrap to 1.69.0Josh Stone-402/+291
2023-04-26Update to LLVM 16.0.2Nikita Popov-0/+0
(cherry picked from commit 935b95630a90acf50ff0c0d1bbd07c7f8f9d1150)
2023-04-17add support for `// unset-exec-env` in compiletestPietro Albini-4/+32
2023-04-17treat the dev channel as nightly in compiletestPietro Albini-1/+5
2023-04-16bump the channel to betaPietro Albini-1/+1
2023-04-15Auto merge of #110335 - asomers:rust-gdb-freebsd, r=jyn514bors-3/+3
Fix rust-gdb on FreeBSD "\w" is a GNU-specific extension to sed. Avoid it. Fixes #110334 Signed-off-by: Alan Somers <asomers@gmail.com>
2023-04-15Auto merge of #109802 - notriddle:notriddle/rustdoc-search-generics-nested, ↵bors-11/+21
r=GuillaumeGomez rustdoc-search: add support for nested generics This change allows `search.js` to parse nested generics (which look `Like<This<Example>>`) and match them. It maintains the existing "bag semantics", so that the order of type parameters is ignored but the number is required to be greater than or equal to what's in the query. For example, a function with the signature `fn read_all(&mut self: impl Read) -> Result<Vec<u8>, Error>` will match these queries: * `Read -> Result<Vec<u8>, Error>` * `Read -> Result<Error, Vec>` * `Read -> Result<Vec<u8>>` But it *does not* match `Result<Vec, u8>` or `Result<u8<Vec>>`.
2023-04-14Typo fix in src/etc/rust-gdbAlan Somers-1/+1
Co-authored-by: SNCPlay42 <SNCPlay42@gmail.com>
2023-04-15Auto merge of #110142 - Mark-Simulacrum:reduce-core-counts, r=pietroalbinibors-64/+72
Reduce core counts for a number of builders Best reviewed by-commit; first commit renames all builder names to include core counts. Applied changes for these builders (only on the auto branch, haven't touched PR CI): - arm-android -> 8 core (currently at 39 minutes; 25.58% CPU) - armhf-gnu -> 8 core (currently at 31 minutes; 30.97% CPU) - dist-aarch64-linux -> 8 core (currently at 35 minutes; 55.38% CPU) - dist-android -> 8 core (currently at 18 minutes; 43.03% CPU) - dist-armhf-linux -> 8 core (currently at 27 minutes; 54.71% CPU) - dist-armv7-linux -> 8 core (currently at 29 minutes; 50.33% CPU) - dist-i586-gnu-i586-i686-musl -> 8 core (currently at 27 minutes; 48.31% CPU) - dist-i686-linux -> 8 core (currently at 32 minutes; 52.39% CPU) - dist-mips-linux -> 8 core (currently at 25 minutes; 55.09% CPU) - dist-mips64-linux -> 8 core (currently at 25 minutes; 55.33% CPU) - dist-mips64el-linux -> 8 core (currently at 26 minutes; 54.93% CPU) - dist-mipsel-linux -> 8 core (currently at 25 minutes; 55.38% CPU) - dist-powerpc-linux -> 8 core (currently at 26 minutes; 55.77% CPU) - dist-powerpc64-linux -> 8 core (currently at 27 minutes; 55.03% CPU) - dist-powerpc64le-linux -> 8 core (currently at 27 minutes; 54.95% CPU) - dist-riscv64-linux -> 8 core (currently at 26 minutes; 54.43% CPU) - dist-s390x-linux -> 8 core (currently at 30 minutes; 55.97% CPU) - dist-various-1 -> 8 core (currently at 36 minutes; 29.16% CPU) - dist-various-2 -> 8 core (currently at 27 minutes; 32.69% CPU) - dist-x86_64-freebsd -> 8 core (currently at 27 minutes; 51.69% CPU) - dist-x86_64-illumos -> 8 core (currently at 30 minutes; 54.88% CPU) - dist-x86_64-musl -> 8 core (currently at 39 minutes; 57.56% CPU) - dist-x86_64-netbsd -> 8 core (currently at 26 minutes; 55.82% CPU) - mingw-check -> 8 core (currently at 17 minutes; 35.00% CPU) - test-various -> 8 core (currently at 22 minutes; 44.84% CPU) - wasm32 -> 8 core (currently at 19 minutes; 62.94% CPU) - x86_64-gnu -> 8 core (currently at 32 minutes; 50.31% CPU) - x86_64-gnu-stable -> 8 core (currently at 32 minutes; 51.23% CPU) - x86_64-gnu-aux -> 8 core (currently at 22 minutes; 46.39% CPU) - x86_64-gnu-debug -> 8 core (currently at 21 minutes; 53.93% CPU) - x86_64-gnu-distcheck -> 8 core (currently at 38 minutes; 55.93% CPU) - x86_64-gnu-llvm-15 -> 8 core (currently at 34 minutes; 52.99% CPU) - x86_64-gnu-llvm-14 -> 8 core (currently at 34 minutes; 52.09% CPU) - x86_64-gnu-llvm-14-stage1 -> 8 core (currently at 33 minutes; 51.13% CPU) - x86_64-gnu-nopt -> 8 core (currently at 29 minutes; 53.36% CPU) - x86_64-gnu-tools -> 8 core (currently at 22 minutes; 40.56% CPU) We may also want to look at merging some of these builders in the future (to deduplicate stage0 builds and such) but that can happen separately - and is more work than just adjusting core counts. r? `@pietroalbini`
2023-04-14Fix rust-gdb and rust-gdbgui on FreeBSDAlan Somers-3/+3
"\w" is a GNU-specific extension to sed. Avoid it. Fixes #110334 Signed-off-by: Alan Somers <asomers@gmail.com>
2023-04-14Update how-to-read-rustdoc.mdMichael Howell-0/+11
2023-04-14rustdoc-search: add support for nested genericsMichael Howell-11/+10
2023-04-14Auto merge of #110197 - cjgillot:codegen-discr, r=pnkfelixbors-1/+1
Do not attempt to commute comparison and cast to codegen discriminants The general algorithm to compute a discriminant is: ``` relative_tag = tag - niche_start is_niche = relative_tag <= (ule) relative_max discr = if is_niche { cast(relative_tag) + niche_variants.start() } else { untagged_variant } ``` We have an optimization branch which attempts to merge the addition and the subtraction by commuting them with the cast. We currently get this optimization wrong. This PR takes the easiest and safest way: remove the optimization, and let LLVM handle it. (Perf may not agree with that course of action :sweat_smile:) There may be a less invasive solution, but I don't have the necessary knowledge of LLVM semantics to find it. Cranelift has the same optimization, which should be handled similarly. cc `@nikic` and `@bjorn3` if you have a better solution. Fixes https://github.com/rust-lang/rust/issues/110128
2023-04-14Auto merge of #110331 - matthiaskrgr:rollup-9vldvow, r=matthiaskrgrbors-17/+12
Rollup of 7 pull requests Successful merges: - #108687 (Reformulate `point_at_expr_source_of_inferred_type` to be more accurate) - #109272 (Add Command environment variable inheritance docs) - #109947 (Add links from `core::cmp` derives to their traits) - #110110 (Use `Display` in top-level example for `PanicInfo`) - #110154 (Fix typos in library) - #110244 (Remove some unneeded imports / qualified paths) - #110328 ([rustdoc] Add explanations for auto-disambiguation when an intra doc link is resolved to a proc-macro and a trait at the same time) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2023-04-14Rollup merge of #110328 - GuillaumeGomez:auto-disambiguation-proc-trait, ↵Matthias Krüger-0/+7
r=notriddle [rustdoc] Add explanations for auto-disambiguation when an intra doc link is resolved to a proc-macro and a trait at the same time Part of https://github.com/rust-lang/rust/issues/110111. r? `@notriddle`
2023-04-14Rollup merge of #110244 - kadiwa4:unnecessary_imports, r=JohnTitorMatthias Krüger-17/+5
Remove some unneeded imports / qualified paths Continuation of #105537.
2023-04-14Add explanations for auto-disambiguation when an intra doc link is resolved ↵Guillaume Gomez-0/+7
to a proc-macro and a trait at the same time
2023-04-14Auto merge of #110263 - jyn514:ui-fulldeps-llvm, r=albertlarsan68bors-4/+24
Add `libLLVM.so` to the target libdir when download-rustc is enabled Previously, we would only add it to the host libdir, which meant it couldn't be loaded by `ui-fulldeps` tests that used rustc_private. Fixes https://github.com/rust-lang/rust/issues/110225, fixes https://github.com/rust-lang/rust/issues/110226.
2023-04-14Pacify tidy.Camille GILLOT-1/+1
2023-04-14Auto merge of #110324 - JohnTitor:rollup-jq31pd1, r=JohnTitorbors-83/+473
Rollup of 7 pull requests Successful merges: - #103682 (Stabilize rustdoc `--test-run-directory`) - #106249 (Create "suggested tests" tool in `rustbuild`) - #110047 (Add link to `collections` docs to `extend` trait) - #110269 (Add `tidy-alphabetical` to features in `core`) - #110292 (Add `tidy-alphabetical` to features in `alloc` & `std`) - #110305 (rustdoc-search: use ES6 `Map` and `Set` where they make sense) - #110315 (Add a stable MIR way to get the main function) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2023-04-14Rollup merge of #110305 - notriddle:notriddle/es6-map-set, r=GuillaumeGomezYuki Okushi-58/+73
rustdoc-search: use ES6 `Map` and `Set` where they make sense Since all supported browsers now support these classes, and rustdoc has started using them in some places, it might as well use them everywhere it makes sense (because, as [MDN's Map page] says, it "performs better in scenarios involving frequent additions and removals of key-value pairs."). [MDN's Map page]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map
2023-04-14Rollup merge of #106249 - Ezrashaw:suggest-test-tool, r=jyn514,albertlarsan68Yuki Okushi-23/+373
Create "suggested tests" tool in `rustbuild` Not the claimed person in #97339 but: I've done a very rough implementation of this feature in-tree. I'm very new to `rustc` development (outside of docs) so some help would be greatly appreciated. The UI of this new subcommand obviously will change and I need some mentoring with the `--run` flag. r? ```@jyn514```
2023-04-14Rollup merge of #103682 - Swatinem:stable-run-directory, r=GuillaumeGomezYuki Okushi-2/+27
Stabilize rustdoc `--test-run-directory` This should resolve https://github.com/rust-lang/rust/issues/84674
2023-04-14Auto merge of #110177 - RalfJung:miri-tests, r=oli-obkbors-1/+4
fix running Miri tests This partially reverts https://github.com/rust-lang/rust/pull/108659 to fix https://github.com/rust-lang/rust/issues/110102: the Miri test runner does not support any flags, they are interpreted as filters instead which leads to no tests being run. I have not checked any of the other test runners for whether they are having any trouble with these flags. Cc `@pietroalbini` `@Mark-Simulacrum` `@jyn514`
2023-04-14Rollup merge of #110279 - GuillaumeGomez:compiler-macro-derive, r=notriddleMatthias Krüger-40/+55
rustdoc: Correctly handle built-in compiler proc-macros as proc-macro and not macro Part of https://github.com/rust-lang/rust/issues/110111. There were actually one issue split in two parts: * Compiler built-in proc-macro were incorrectly considered as macros and not proc-macros. * Re-exports of compiler built-in proc-macros were considering them as macros. Both issues can be fixed by looking at the `MacroKind` variant instead of just relying on information extracted later on. r? ``@fmease``
2023-04-14Auto merge of #109875 - jyn514:no-fulldeps, r=compiler-errorsbors-1/+1
Move most ui-fulldeps tests to ui/ Same rationale as https://github.com/rust-lang/rust/pull/109770, they don't actually need a stage 2 build. This increases the limit for the UI directory because otherwise it was annoying to be constantly moving files into subdirectories when I fixed a test; https://github.com/rust-lang/rust/pull/109873 makes up for it. cc https://github.com/rust-lang/rust/pull/109770, https://github.com/rust-lang/rust/pull/109874
2023-04-13Move most ui-fulldeps tests to uijyn-1/+1
They pass fine. Only tests that required `extern crate rustc_*` or were marked `ignore-stage1` have been keep in fulldeps.
2023-04-14Auto merge of #110160 - petrochenkov:notagain2, r=cjgillotbors-5/+5
resolve: Pre-compute non-reexport module children Instead of repeating the same logic by walking HIR during metadata encoding. The only difference is that we are no longer encoding `macro_rules` items, but we never currently need them as a part of this list. They can be encoded separately if this need ever arises. `module_reexports` is also un-querified, because I don't see any reasons to make it a query, only overhead.
2023-04-13rustdoc-search: use ES6 Map for `Result` instead of ObjectMichael Howell-21/+40
2023-04-13rustdoc-search: use ES6 `Set` for deduplication instead of `Object`Michael Howell-3/+3
2023-04-13rustdoc-search: use ES6 `Map` for generic matching instead of `Object`Michael Howell-23/+14
2023-04-13rustdoc-search: use ES6 `Map` for aliases instead of `Object`Michael Howell-11/+16
2023-04-13Auto merge of #110253 - weihanglo:update-cargo, r=weihanglobors-0/+0
Update cargo 4 commits in 7bf43f028ba5eb1f4d70d271c2546c38512c9875..84b7041fd2745ee6b3b4a150314f81aabb78e6b2 2023-04-10 16:01:41 +0000 to 2023-04-13 20:08:40 +0000 - Stabilize `cargo logout` (rust-lang/cargo#11950) - Add more information to HTTP errors to help with debugging. (rust-lang/cargo#11878) - Use registry.default for login/logout (rust-lang/cargo#11949) - Change -C to be unstable (rust-lang/cargo#11960)
2023-04-13Update cargoWeihang Lo-0/+0
2023-04-13Rollup merge of #110265 - KittyBorgX:master, r=ozkanonurMatthias Krüger-0/+6
Automatically update the LLVM submodule for musl target (and other places) Fixes #109987
2023-04-13Auto merge of #109989 - ids1024:m68k-asm, r=Amanieubors-1/+13
Add inline assembly support for m68k I believe this should be correct, to the extent I understand the logic around inline assembly. M68k is fairly straightforward here, other than having separate address registers.
2023-04-13Correctly handle built-in compiler proc-macros as proc-macro and not macroGuillaume Gomez-40/+55
2023-04-13Rollup merge of #110072 - joshtriplett:stabilize-is-terminal, r=Mark-SimulacrumMatthias Krüger-5/+0
Stabilize IsTerminal FCP completed in https://github.com/rust-lang/rust/issues/98070 . closes: https://github.com/rust-lang/rust/issues/98070
2023-04-13Auto merge of #109786 - estebank:tweak-add-line-sugg, r=compiler-errorsbors-11/+19
Tweak output for 'add line' suggestion Closes #108174
2023-04-13automatically update the LLVM submoduleKrishna Ramasimha-0/+6
2023-04-12Add `libLLVM.so` to the target libdir when download-rustc is enabledjyn-4/+24
Previously, we would only add it to the host libdir, which meant it couldn't be loaded by `ui-fulldeps` tests that used rustc_private.
2023-04-12Add inline assembly support for m68kIan Douglas Scott-1/+13
2023-04-12Special-case item attributes in the suggestion outputEsteban Küber-9/+0
2023-04-12Tweak output for 'add line' suggestionEsteban Küber-11/+28
2023-04-12Auto merge of #110252 - matthiaskrgr:rollup-ovaixra, r=matthiaskrgrbors-88/+89
Rollup of 8 pull requests Successful merges: - #109810 (Replace rustdoc-ui/{c,z}-help tests with a stable run-make test ) - #110035 (fix: ensure bad `#[test]` invocs retain correct AST) - #110089 (sync::mpsc: synchronize receiver disconnect with initialization) - #110103 (Report overflows gracefully with new solver) - #110122 (Fix x check --stage 1 when download-ci-llvm=false) - #110133 (Do not use ImplDerivedObligationCause for inherent impl method error reporting) - #110135 (Revert "Don't recover lifetimes/labels containing emojis as character literals") - #110235 (Fix `--extend-css` option) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-07 09:27:29 +0000