about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2023-09-15Add documentation for `custom_code_classes_in_docs` featureGuillaume Gomez-0/+29
2023-09-15Add tests for `custom_code_classes_in_docs` featureGuillaume Gomez-27/+104
2023-09-15Implement custom classes for rustdoc code blocks with ↵Guillaume Gomez-49/+318
`custom_code_classes_in_docs` feature
2023-09-16Update cargoWeihang Lo-0/+0
2023-09-15rustdoc: avoid calling `document.write` after the page loadsMichael Howell-2/+12
2023-09-15rustdoc: merge theme css into rustdoc.cssMichael Howell-446/+795
Based on https://github.com/rust-lang/rust/pull/115812#issuecomment-1717960119 Having them in separate files used to make more sense, before the migration to CSS variables made the theme files as small as they are nowadays. This is already how docs.rs and mdBook do it.
2023-09-15avoid blessing cargo deps's source code in ui testsPietro Albini-0/+10
2023-09-15Auto merge of #115851 - Alexendoo:clippy-doc-hidden-headers, r=flip1995bors-1/+20
Ignore `#[doc(hidden)]` functions in clippy doc lints Fixes https://github.com/rust-lang/rust-clippy/issues/11501 The implementation before #115689 had a check for unsugared doc comments that also happened to catch `#[doc(hidden)]`, this adds the check back in more explicitly https://github.com/rust-lang/rust/blob/852bf4e51bf260550cd1a280d2146f1c0641b1e8/src/tools/clippy/clippy_lints/src/doc.rs#L526-L529 r? `@flip1995`
2023-09-15Merge from rustcThe Miri Conjob Bot-1857/+4922
2023-09-15Preparing for merge from rustcThe Miri Conjob Bot-1/+1
2023-09-14don't point at const usage site for resolution-time errorsRalf Jung-6/+6
also share the code that emits the actual error
2023-09-14move required_consts check to general post-mono-check functionRalf Jung-5/+4
2023-09-14Auto merge of #115677 - matthewjasper:let-expr-recovery, r=b-naberbors-4/+4
Improve invalid let expression handling - Move all of the checks for valid let expression positions to parsing. - Add a field to ExprKind::Let in AST/HIR to mark whether it's in a valid location. - Suppress some later errors and MIR construction for invalid let expressions. - Fix a (drop) scope issue that was also responsible for #104172. Fixes #104172 Fixes #104868
2023-09-14Ignore `#[doc(hidden)]` functions in clippy doc lintsAlex Macleod-1/+20
2023-09-14Auto merge of #115817 - fee1-dead-contrib:fix-codegen, r=oli-obkbors-1/+1
treat host effect params as erased in codegen This fixes the changes brought to codegen tests when effect params are added to libcore, by not attempting to monomorphize functions that get the host param by being `const fn`. r? `@oli-obk`
2023-09-14fix clippy (and MIR printing) handling of ConstValue::Indirect slicesRalf Jung-13/+4
2023-09-14update SETTINGS_HASHESRalf Jung-0/+1
2023-09-14update rust_analyzer_settings.jsonRalf Jung-2/+2
2023-09-14treat host effect params as erased generics in codegenDeadbeef-1/+1
This fixes the changes brought to codegen tests when effect params are added to libcore, by not attempting to monomorphize functions that get the host param by being `const fn`.
2023-09-14make it more clear which functions create fresh AllocIdRalf Jung-6/+6
2023-09-14cleanup op_to_const a bit; rename ConstValue::ByRef → IndirectRalf Jung-2/+2
2023-09-14use AllocId instead of Allocation in ConstValue::ByRefRalf Jung-25/+28
2023-09-14Auto merge of #114656 - bossmc:rework-no-coverage-attr, r=oli-obkbors-12/+12
Rework `no_coverage` to `coverage(off)` As discussed at the tail of https://github.com/rust-lang/rust/issues/84605 this replaces the `no_coverage` attribute with a `coverage` attribute that takes sub-parameters (currently `off` and `on`) to control the coverage instrumentation. Allows future-proofing for things like `coverage(off, reason="Tested live", issue="#12345")` or similar.
2023-09-13Auto merge of #115790 - flip1995:clippyup, r=Manishearthbors-1635/+4682
Update Clippy r? `@Manishearth`
2023-09-13rustc_middle: add `Scalar::from_i8` and `Scalar::from_i16` and use them in MiriEduardo Sánchez Muñoz-9/+5
2023-09-13Rollup merge of #115812 - GuillaumeGomez:merge-settings-into-rustdoc-css, ↵Matthias Krüger-76/+64
r=notriddle Merge settings.css into rustdoc.css There aren't that many CSS rules in `settings.css`, however quite some code is needed around it, making it more costly than useful. I think it's better to merge into `rustdoc.css` to simplify this. r? `@notriddle`
2023-09-13Resolve clippy warningsJakub Beránek-8/+6
2023-09-13Refactor rustc-perf buildingJakub Beránek-11/+13
2023-09-13Auto merge of #115803 - RalfJung:const-eval, r=oli-obkbors-12/+4
make the eval() functions on our const types return the resulting value This is a part of https://github.com/rust-lang/rust/pull/115748 that's hopefully perf-neutral, and that does not depend on https://github.com/rust-lang/rust/pull/115764.
2023-09-13Merge settings.css into rustdoc.cssGuillaume Gomez-76/+64
2023-09-13Adjust commentKai Luo-2/+2
2023-09-13Adjust commentKai Luo-2/+2
2023-09-13Add comment to elaborateKai Luo-0/+6
2023-09-13Make AIX known by bootstrapKai Luo-0/+2
2023-09-13make the set of methods between our two Const types more consistentRalf Jung-10/+2
2023-09-13make the eval() functions on our const types return the resulting valueRalf Jung-2/+2
2023-09-13Auto merge of #115706 - RalfJung:compiletest-truncation, r=wesleywiserbors-70/+74
Make compiletest output truncation less disruptive When the test output becomes too large, compiletest stops recording all of it. However: - this can lead to invalid JSON, which then causes compiletest itself to throw further errors - the note that output was truncated is in the middle of the output, with >100kb of text on each side; that makes it almost impossible to actually see that note in the terminal So assuming that we do need to keep the output truncation, I propose that we only ever do a cut at the end, so that it is very clear by looking at the end of the log that truncation happened. I added a message at the beginning of the output as well. Also I added some logic to make it less likely that we'll cut things off in the middle of a JSON record. (I tested that successfully by reducing the output limit to something very low and running a few ui tests.) Furthermore I increased the max buffer size to 512KB; that's really not a lot of memory compared to how much RAM it takes to build rustc (it's ~25% more than the previous maximum HEAD+TAIL length). And finally, the information that things got truncated is now propagated to the higher levels, so that we can fail the test instead of comparing the truncated output with the reference. Fixes https://github.com/rust-lang/rust/issues/115675 Fixes https://github.com/rust-lang/rust/issues/96229 Fixes https://github.com/rust-lang/rust/issues/94322 Fixes https://github.com/rust-lang/rust/issues/92211
2023-09-12Auto merge of #115800 - RalfJung:miri, r=RalfJungbors-83/+1935
update Miri r? `@ghost`
2023-09-12Auto merge of #115128 - davidtwco:re-enable-debuginfo-test, r=wesleywiserbors-0/+9
tests: re-enable pretty-std-collections on macOS Fixes #78665. I made some small modifications to this test so that it would pass for me locally (though I was only able to test using lldb without built-in Rust support, but that seems to be the mode in which it would fail). I ran it a few hundred times with stage one and stage two to see if I could re-produce the spurious failures that were being reported in #78665 and couldn't. From the discussion in #78665, it seemed like this was related to Xcode versions and could be reproduced locally fairly easily. It's been a couple years since this was disabled so a lot has changed. If this starts failing spuriously again then we can disable it and I can look into that. r? `@wesleywiser` (discussed in wg-debugging's triage meeting)
2023-09-12Auto merge of #3055 - eduardosm:x86-sse2-intrinsics, r=RalfJungbors-57/+1894
Implement some `llvm.x86.sse2.*` intrinsics and add tests Continuation of https://github.com/rust-lang/miri/pull/2989 with SSE2 intrinsics. Thankfully, a significant amount of SSE2 functions use `simd_*` intrinsics, which are already implemented in Miri.
2023-09-12Implement some `llvm.x86.sse2.*` intrinsics and add testsEduardo Sánchez Muñoz-51/+1869
Implements LLVM intrisics needed to run most SSE2 functions from `core::arch::x86{,_64}`. Also adds miri tests for those functions (mostly copied from core_arch tests).
2023-09-12Ignore all archs except x86 and x86_64 in SSE testsEduardo Sánchez Muñoz-2/+21
2023-09-12Add a Local environment to `opt-dist`Jakub Beránek-5/+77
This makes it easier to build a PGO/BOLT optimized `rustc` locally, outside of CI.
2023-09-12Fix `reset_directory` functionJakub Beránek-1/+1
Before it was not deleting non-empty directories.
2023-09-12Refactor EnvironmentJakub Beránek-274/+262
2023-09-12Fix a few typos in shims/x86/sse.rs commentsEduardo Sánchez Muñoz-4/+4
2023-09-12Merge commit '98363cbf6a7c3f8b571a7d92a3c645bb4376e4a6' into clippyupPhilipp Krones-1635/+4682
2023-09-12Make executable extension platform, rather than environment dependentJakub Beránek-20/+20
2023-09-12Store target triple in environmentJakub Beránek-10/+27
2023-09-12extra ABI tests, in particular for DispatchFromDynRalf Jung-6/+16
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 05:18:57 +0000