about summary refs log tree commit diff
path: root/src/tools
AgeCommit message (Collapse)AuthorLines
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-6/+6
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-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-10/+2
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-13make the set of methods between our two Const types more consistentRalf Jung-10/+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-272/+260
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
2023-09-12fmtThe Miri Conjob Bot-1/+3
2023-09-12Merge from rustcThe Miri Conjob Bot-246/+383
2023-09-12Preparing for merge from rustcThe Miri Conjob Bot-1/+1
2023-09-12Auto merge of #115699 - RalfJung:interpret-abi-compat, r=oli-obkbors-29/+60
interpret: change ABI-compat test to be type-based This makes the test consistent across targets. Otherwise the chances are very high that ABI mismatches get accepted on x86_64 but still fail on many other targets with more complicated ABIs. This implements (most of) the rules described in https://github.com/rust-lang/rust/pull/115476.
2023-09-12Auto merge of #115689 - Alexendoo:clippy-doc-comments, ↵bors-157/+160
r=notriddle,Manishearth,flip1995 Reuse rustdoc's doc comment handling in Clippy Moves `source_span_for_markdown_range` and `span_of_attrs` (renamed to `span_of_fragments`) to `rustc_resolve::rustdoc` so it can be used in Clippy Fixes https://github.com/rust-lang/rust-clippy/issues/10277 Fixes https://github.com/rust-lang/rust-clippy/issues/5593 Fixes https://github.com/rust-lang/rust-clippy/issues/10263 Fixes https://github.com/rust-lang/rust-clippy/issues/2581
2023-09-11Rollup merge of #115730 - bjorn3:some_driver_refactors, r=compiler-errorsMatthias Krüger-2/+2
Some more small driver refactors To improve clarity and simplify some code.
2023-09-11enforce no-merge policy via triagebotRalf Jung-1/+4
2023-09-11Update tools and fulldeps testsMatthew Jasper-4/+4
2023-09-11add subtree-sync label to rustc update PRsPeter Jaszkowiak-1/+5
2023-09-10Call `LateLintPass::check_attribute` from `with_lint_attrs`Alex Macleod-7/+21
2023-09-10Remove EarlyErrorHandler argument from after_analysis callbackbjorn3-2/+2
It is only used by miri which can create a new one using the Session.
2023-09-09don't even try to compare with reference when there was truncationRalf Jung-7/+43
2023-09-09compiletest: only truncate at the end, to make it more clearly visibleRalf Jung-63/+31
2023-09-09implement and test ABI compatibility for transparent wrappers around NPO typesRalf Jung-5/+8
2023-09-09implement and test fn ptr ABI compatibility rulesRalf Jung-0/+5
2023-09-09give extra context to ABI mismatch errorsRalf Jung-8/+28
2023-09-09interpret: change ABI-compat test to be type-based, so the test is ↵Ralf Jung-18/+21
consistent across targets
2023-09-09Update cargoWeihang Lo-0/+0
2023-09-08Reuse rustdoc's doc comment handling in ClippyAlex Macleod-157/+160
2023-09-08Use `#!/usr/bin/env` shebang Nilstrieb-1/+1
``` $ ls /bin/bash ls: cannot access '/bin/bash': No such file or directory ``` On certain systems, `/bin` and `/usr/bin` are nothing but wastelands, with just `env`around as the last survivor of the great purge. The binaries have cowardly hidden away and only `env` can show us the way to greatness (bash). ❄️
2023-09-08Auto merge of #115418 - Zoxc:freeze-source, r=oli-obkbors-47/+39
Use `Freeze` for `SourceFile` This uses the `Freeze` type in `SourceFile` to let accessing `external_src` and `lines` be lock-free. Behavior of `add_external_src` is changed to set `ExternalSourceKind::AbsentErr` on a hash mismatch which matches the documentation. `ExternalSourceKind::Unneeded` was removed as it's unused. Based on https://github.com/rust-lang/rust/pull/115401.
2023-09-08Partially outline code inside the panic! macroJohn Kåre Alsaker-23/+52
2023-09-08Rework no_coverage to coverage(off)Andy Caldwell-6/+6
2023-09-08Auto merge of #115608 - RalfJung:fn-arg-validity, r=oli-obkbors-4/+101
miri: catch function calls where the argument is caller-invalid / the return value callee-invalid When doing a type-changing copy, we must validate the data both at the old and new type. Fixes https://github.com/rust-lang/miri/issues/3017
2023-09-07Use `Freeze` for `SourceFile.lines`John Kåre Alsaker-47/+39
2023-09-06miri: catch function calls where the argument is caller-invalid / the return ↵Ralf Jung-4/+101
value callee-invalid
2023-09-06fmtRalf Jung-13/+9
2023-09-06Merge from rustcRalf Jung-119/+1585
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 19:56:58 +0000