about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2025-07-08tidy: warn when --extra-checks is passed an invalid lang:kind combobinarycat-3/+25
Co-authored-by: Jakub Beránek <berykubik@gmail.com>
2025-07-08tidy: add `auto:` prefix to --extra-checks syntaxbinarycat-20/+67
currently this just uses a very simple extension-based heirustic.
2025-07-08tidy: update files_modified to take CiInfobinarycat-3/+7
2025-07-08tidy: factor out change detection logic and make it more robustbinarycat-16/+30
now does proper parsing of git's output and falls back to assuming all files are modified if `git` doesn't work. accepts a closure so extensions can be checked.
2025-07-08Revert "Re-enable fixpoint iteration for variance computation"Chayim Refael Friedman-13/+13
2025-07-08SpellingAleksey Kliger-1/+1
2025-07-08tidy: refactor --extra-checks parsingbinarycat-14/+111
2025-07-08Rollup merge of #143622 - ↵Matthias Krüger-1/+51
Gelbpunkt:mips64-unknown-linux-muslabi64-target-maintainer, r=jieyouxu Add target maintainer information for mips64-unknown-linux-muslabi64 The `mips64-unknown-linux-muslabi64` target is currently rather broken, but I'm working on getting it fixed so that it can at least be used again. While I can't commit to maintaining the LLVM side of this target, I don't mind looking into any other MIPS or musl-related issues that arise with this target. See e.g. rust-lang/rust#143409 for some rustc fixes I have in the pipeline and https://github.com/rust-lang/libc/pull/4509, https://github.com/rust-lang/libc/pull/4527, https://github.com/rust-lang/libc/pull/4528, https://github.com/rust-lang/libc/pull/4529, https://github.com/rust-lang/libc/pull/4530 for fixing the libc definitions for this target. I'm adding myself as a maintainer mostly due to [this interaction](https://github.com/rust-lang/libc/pull/4530#issuecomment-3045912645). LLVM support has been a concern for these targets in the past, but it shouldn't hurt to have a nominal maintainer for these even if they remain tier 3. From my experience, LLVM for MIPS is working well nowadays unless you decide to use LLD, which is horribly broken on MIPS.
2025-07-08Rollup merge of #143600 - alexcrichton:wasm32-wasip1-doc-reword, r=jieyouxuMatthias Krüger-25/+23
Update intro blurb in `wasm32-wasip1` docs I was reading over this documentation in light of the effort to enlist more maintainers for Tier 2 targets and figured it was time for a refresh of this documentation now that historical renames/etc have all become a thing of the past. No new major changes to this documentation, mostly just wanted to update it and reflect the modern status quo for this target.
2025-07-08Rollup merge of #143555 - ↵Matthias Krüger-1/+14
obi1kenobi:pg/target-feature-not-unsafe-rustdoc-json, r=aDotInTheVoid Don't mark `#[target_feature]` safe fns as unsafe in rustdoc JSON. Fixes https://github.com/rust-lang/rust/issues/142655 by explicitly checking whether functions are safe but using `#[target_feature]`, instead of relying on the `FnHeader::is_unsafe()` method which considers such functions unsafe. I don't believe this merits a bump of the rustdoc JSON `FORMAT_VERSION` constant, since the format is unchanged and this is just a small bugfix. r? aDotInTheVoid
2025-07-09Migrate `pull_assignment_up` assist to `SyntaxEditor`Hayashi Mikihiro-27/+59
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
2025-07-08Fix weird rustdoc output when single and glob reexport conflict on a nameGuillaume Gomez-40/+84
2025-07-08Auto merge of #134628 - estebank:const-default, r=oli-obkbors-2/+4
Make `Default` const and add some `const Default` impls Full list of `impl const Default` types: - () - bool - char - std::ascii::Char - usize - u8 - u16 - u32 - u64 - u128 - i8 - i16 - i32 - i64 - i128 - f16 - f32 - f64 - f128 - std::marker::PhantomData<T> - Option<T> - std::iter::Empty<T> - std::ptr::Alignment - &[T] - &mut [T] - &str - &mut str - String - Vec<T>
2025-07-08Implement enter_trace_span() in MiriMachineStypox-2/+10
2025-07-08Add cross-compilation tool testJakub Beránek-0/+29
2025-07-08Rewrite for clarityAleksey Kliger-12/+14
move common code to a helper function Co-Authored-By: Kobzol <berykubik@gmail.com>
2025-07-08document new stable flags, with x64 linux implementation notesRémy Rakic-43/+59
2025-07-08update to literal-escaper-0.0.5Marijn Schouten-1/+1
2025-07-08Also test `LldWrapper` and remove `llvm-config` override from testsJakub Beránek-3/+10
2025-07-08Update llvm-bitcode-linker testsJakub Beránek-5/+35
2025-07-08Remove sysroot copy from `LlvmBitcodeLinker` stepJakub Beránek-20/+10
That step should be responsible for building the tool, not performing side-effects. Also, only copy the tool to the `self-contained` directory, not to the `rustlib/<target>/bin` directory.
2025-07-08Remove `extra_features` from `LlvmBitcodeLinker`Jakub Beránek-6/+2
It wasn't used anywhere.
2025-07-08update bootstrap mcp510 handlingRémy Rakic-16/+46
beta and stage1 need to use different flags (-C vs -Z) to be able to use the old and new `linker-features` and `link-self-contained` flags
2025-07-08add post-dist test for checking that we use LLDRémy Rakic-0/+3
And remove the previous beta/stable/nightly LLD tests.
2025-07-08use LLD by default on x64 regardless of channelRémy Rakic-7/+2
2025-07-08Merge pull request #4454 from RalfJung/data_structureOli Scherer-25/+26
move our data structures into a central location
2025-07-08Fix handling of std crates for no_std targetsJakub Beránek-41/+106
2025-07-08Add `crates` metadata to `doc::Std` stepJakub Beránek-20/+24
2025-07-08Remove test hack for std cratesJakub Beránek-5/+0
2025-07-08Mention that stdarch is managed by josh-syncJakub Beránek-2/+3
2025-07-08Merge from rustcRalf Jung-1140/+1693
2025-07-08Auto merge of #142869 - nnethercote:join_path-mini, r=camelidbors-2/+2
Use `join_with_double_colon` in `write_shared.rs`. For consistency. Also, it's faster because `join_with_double_colon` does a better job estimating the allocation size than `join` from `itertools`. r? `@camelid`
2025-07-08Preparing for merge from rustcRalf Jung-1/+1
2025-07-08Merge pull request #20192 from ChayimFriedman2/link-type-panicLukas Wirth-3/+30
fix: Fix a case where the link type was `None`
2025-07-08Don't mark `#[target_feature]` safe fns as unsafe in rustdoc JSON.Predrag Gruevski-1/+14
2025-07-08Add target maintainer information for mips64-unknown-linux-muslabi64Jens Reidel-1/+51
The mips64-unknown-linux-muslabi64 target is currently rather broken, but I'm working on getting it fixed so that it can at least be used again. While I can't commit to maintaining the LLVM side of this target, I don't mind looking into any other MIPS or musl-related issues that arise with this target. Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2025-07-07Account for const stability in clippy when checking constnessEsteban Küber-6/+14
2025-07-07Make `Default` const and add some `const Default` implsEsteban Küber-10/+4
Full list of `impl const Default` types: - () - bool - char - Cell - std::ascii::Char - usize - u8 - u16 - u32 - u64 - u128 - i8 - i16 - i32 - i64 - i128 - f16 - f32 - f64 - f128 - std::marker::PhantomData<T> - Option<T> - std::iter::Empty<T> - std::ptr::Alignment - &[T] - &mut [T] - &str - &mut str - String - Vec<T>
2025-07-07Make it possible to attach opaque string metadata to `StepMetadata`Jakub Beránek-2/+12
2025-07-07Auto merge of #143601 - matthiaskrgr:rollup-9iw2sqk, r=matthiaskrgrbors-43/+39
Rollup of 9 pull requests Successful merges: - rust-lang/rust#132469 (Do not suggest borrow that is already there in fully-qualified call) - rust-lang/rust#143340 (awhile -> a while where appropriate) - rust-lang/rust#143438 (Fix the link in `rustdoc.md`) - rust-lang/rust#143539 (Regression tests for repr ICEs) - rust-lang/rust#143566 (Fix `x86_64-unknown-netbsd` platform support page) - rust-lang/rust#143572 (Remove unused allow attrs) - rust-lang/rust#143583 (`loop_match`: fix 'no terminator on block') - rust-lang/rust#143584 (make `Machine::load_mir` infallible) - rust-lang/rust#143591 (Fix missing words in future tracking issue) r? `@ghost` `@rustbot` modify labels: rollup
2025-07-07Add docstringAleksey Kliger-0/+4
2025-07-07configure.py: Write last key in each sectionAleksey Kliger-0/+4
The loop that writes the keys in each section of bootstrap.toml accumulates all the commented lines before a given key and emits them when it reaches the next key in the section. This ends up dropping lines accumulated for the last key
2025-07-07Merge pull request #20180 from ChayimFriedman2/parser-stuckLukas Wirth-8/+50
fix: Always bump in the parser in `err_and_bump()`
2025-07-07Rollup merge of #143572 - yotamofek:pr/unused-allow-attrs, r=fee1-deadMatthias Krüger-2/+0
Remove unused allow attrs These `#[allow]`s seem to be unused (at least according to `x check`, didn't run `x test` locally). Let's clean them up! 🧹
2025-07-07Rollup merge of #143566 - jieyouxu:fix-x86_64-unknown-netbsd, r=fee1-deadMatthias Krüger-15/+13
Fix `x86_64-unknown-netbsd` platform support page `x86_64-unknown-netbsd` is Tier 2 with host tools, not Tier 3. cc `@he32.` r? compiler
2025-07-07Rollup merge of #143438 - makai410:rustdoc-fix, r=ehussMatthias Krüger-1/+1
Fix the link in `rustdoc.md`
2025-07-07Rollup merge of #143340 - nabijaczleweli:awhile, r=mati865Matthias Krüger-25/+25
awhile -> a while where appropriate
2025-07-07Fix a case where the link type was `None`Chayim Refael Friedman-3/+30
Which caused a panic.
2025-07-07Update intro blurb in `wasm32-wasip1` docsAlex Crichton-25/+23
I was reading over this documentation in light of the effort to enlist more maintainers for Tier 2 targets and figured it was time for a refresh of this documentation now that historical renames/etc have all become a thing of the past. No new major changes to this documentation, mostly just wanted to update it and reflect the modern status quo for this target.
2025-07-07Auto merge of #143182 - xdoardo:more-addrspace, r=workingjubileebors-10/+11
Allow custom default address spaces and parse `p-` specifications in the datalayout string Some targets, such as CHERI, use as default an address space different from the "normal" default address space `0` (in the case of CHERI, [200 is used](https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-877.pdf)). Currently, `rustc` does not allow to specify custom address spaces and does not take into consideration [`p-` specifications in the datalayout string](https://llvm.org/docs/LangRef.html#langref-datalayout). This patch tries to mitigate these problems by allowing targets to define a custom default address space (while keeping the default value to address space `0`) and adding the code to parse the `p-` specifications in `rustc_abi`. The main changes are that `TargetDataLayout` now uses functions to refer to pointer-related informations, instead of having specific fields for the size and alignment of pointers in the default address space; furthermore, the two `pointer_size` and `pointer_align` fields in `TargetDataLayout` are replaced with an `FxHashMap` that holds info for all the possible address spaces, as parsed by the `p-` specifications. The potential performance drawbacks of not having ad-hoc fields for the default address space will be tested in this PR's CI run. r? workingjubilee
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 20:14:27 +0000