- 28 6月, 2022 18 次提交
-
-
由 Krasimir Georgiev 提交于
This adapts llvm-wrapper for https://github.com/llvm/llvm-project/commit/dacfa24f75c328ae30b710ecadaa18e4ba10cdc6, which removed ASanGlobalsMetadataAnalysis.
-
由 bors 提交于
attempt to optimise vectored write benchmarked: old: ``` test io::cursor::tests::bench_write_vec ... bench: 68 ns/iter (+/- 2) test io::cursor::tests::bench_write_vec_vectored ... bench: 913 ns/iter (+/- 31) ``` new: ``` test io::cursor::tests::bench_write_vec ... bench: 64 ns/iter (+/- 0) test io::cursor::tests::bench_write_vec_vectored ... bench: 747 ns/iter (+/- 27) ``` More unsafe than I wanted (and less gains) in the end, but it still does the job
-
由 bors 提交于
Only keep a single query for well-formed checking There are currently 3 queries to perform wf checks on different item-likes. This complexity is not required. This PR replaces the query by: - one query per item; - one query to invoke it for a whole module. This allows to remove HIR `ParItemLikeVisitor`.
-
由 bors 提交于
Rollup of 9 pull requests Successful merges: - #98331 (Fix rustdoc argument error) - #98506 (Fix span issues in object safety suggestions) - #98563 (interpret: refactor allocation info query) - #98576 (small regions refactoring) - #98577 (Fix "kind" for associated types in trait implementations in rustdoc JSON) - #98578 (Remove eddyb from miri failure pings) - #98579 (liballoc tests: avoid int2ptr cast) - #98581 (Add triagebot mentions.) - #98587 (libcore tests: avoid int2ptr casts) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
-
由 Matthias Krüger 提交于
libcore tests: avoid int2ptr casts We don't need any of these pointers to actually be dereferenceable so using `ptr::invalid` should be fine. And then we can run Miri with strict provenance enforcement on the tests.
-
由 Matthias Krüger 提交于
Add triagebot mentions. This migrates the configuration of mentions from highfive to triagebot. I also fixed a few broken paths (error_codes.rs src/librustdoc/html/static/themes src/librustdoc/html/static/themes/ayu.css).
-
由 Matthias Krüger 提交于
liballoc tests: avoid int2ptr cast I think we don't need `ptr::from_exposed_addr` here; `ptr::invalid` should be enough for this test. (And this makes Miri less unhappy when running these tests.)
-
由 Matthias Krüger 提交于
Remove eddyb from miri failure pings r? `@EddyB`
-
由 Matthias Krüger 提交于
Fix "kind" for associated types in trait implementations in rustdoc JSON Fixes https://github.com/rust-lang/rust/issues/81340. Contrary to what is suggested in the issue, I really think we should distinguish between associated items and "normal" constants and types. cc `@CraftSpider` `@SimonSapin` r? `@notriddle`
-
由 Matthias Krüger 提交于
small regions refactoring these commits should be fairly self-contained r? rust-lang/types
-
由 Matthias Krüger 提交于
interpret: refactor allocation info query We now have an infallible function that also tells us which kind of allocation we are talking about. Also we do longer have to distinguish between data and function allocations for liveness. This will help us to avoid "catching" `InterpError`s in Miri. r? `@oli-obk`
-
由 Matthias Krüger 提交于
Fix span issues in object safety suggestions Fixes #98500
-
由 Matthias Krüger 提交于
Fix rustdoc argument error Fixes #88756. It's a take over of #88831. I cherry-picked the commits, fixed the merge conflict and the failing test. cc `@inashivb` `@jyn514` r? `@notriddle`
-
由 bors 提交于
catch unwind in parallel mode during wfcheck Update #75760 When performing wfcheck, from the test results, the parallel mode will stop all checks when an `item`'s check failed, (e.g. the first ui test failure raised from [here](https://github.com/rust-lang/rust/blob/master/compiler/rustc_trait_selection/src/traits/error_reporting/mod.rs#L249))while the serial mode will output each `item`'s check result via `catch_unwind`. This leads to inconsistencies in the final output of the two mode. In my local environment, this modification prevents the following ui tests from failing when set `parallel-compiler = true` in `config.toml`: ``` [ui] src/test\ui\associated-types\defaults-cyclic-fail-1.rs [ui] src/test\ui\associated-types\defaults-cyclic-fail-2.rs [ui] src/test\ui\associated-types\hr-associated-type-bound-2.rs [ui] src/test\ui\associated-types\impl-wf-cycle-1.rs [ui] src/test\ui\associated-types\impl-wf-cycle-2.rs [ui] src/test\ui\issues\issue-20413.rs [ui] src/test\ui\parallel_test\defaults-cyclic-fail-para.rs ```
-
由 Eric Huss 提交于
-
由 Ralf Jung 提交于
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #97389 (Improve memory ordering diagnostics) - #97780 (Check ADT field is well-formed before checking it is sized) - #98530 (compiletest: add issue number param to `known-bug`) - #98556 (Fix builds on Windows (closes #98546)) - #98561 (Fix spelling in SAFETY comment) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
-
- 27 6月, 2022 22 次提交
-
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Oli Scherer 提交于
-
由 lcnr 提交于
-
由 Guillaume Gomez 提交于
-
由 Guillaume Gomez 提交于
-
由 lcnr 提交于
-
由 lcnr 提交于
see comment added to the field in `VerifyBoundCx`.
-
由 Guillaume Gomez 提交于
-
由 Shivani Bhardwaj 提交于
-
由 Shivani Bhardwaj 提交于
-
由 Shivani Bhardwaj 提交于
-
由 SparrowLii 提交于
-
由 Matthias Krüger 提交于
Fix spelling in SAFETY comment "can not" should be "cannot", and add punctuation.
-
由 Matthias Krüger 提交于
Fix builds on Windows (closes #98546) closes https://github.com/rust-lang/rust/issues/98546
-
由 Matthias Krüger 提交于
compiletest: add issue number param to `known-bug` I was getting some errors while testing this, but I'm pretty sure that was unrelated to my changes. Closes #98436 > Basically, instead of `// known-bug`, do `// known-bug #00000` or maybe `// known-bug chalk#00`? > > From: https://rust-lang.zulipchat.com/#narrow/stream/326866-t-types.2Fnominated/topic/.2398095.3A.20NLL.3A.20unsound.20verification.20of.20higher.20ranked.20outlives.E2.80.A6/near/287258738 I also added an `unknown` escape-hatch because I didn't find corresponding issues for every `// known-bug`. The syntax also ended up being `// known-bug: `, because of `set_name_value_directive`.
-
由 Matthias Krüger 提交于
Check ADT field is well-formed before checking it is sized Fixes #96810. There is one diagnostics regression, in [`src/test/ui/generic-associated-types/bugs/issue-80626.stderr`](https://github.com/rust-lang/rust/pull/97780/files#diff-53795946378e78a0af23a10277c628ff79091c18090fdc385801ee70c1ba6963). I am not super concerned about it, since it's GAT related. We _could_ fix it, possibly by using the `FieldSized` obligation cause code instead of `BuiltinDerivedObligation`. But that would require changing `Sized` trait confirmation and the `adt_sized_constraint` query.
-
由 Matthias Krüger 提交于
Improve memory ordering diagnostics Before: ![image](https://user-images.githubusercontent.com/783247/170234545-891cac30-eaa2-4186-847b-35cd51e00f2b.png) After: ![image](https://user-images.githubusercontent.com/783247/170239684-645f186f-5a02-4eb9-8651-2e5fe9591352.png) --- Before this change, the compiler suggests the failure ordering is too strong and suggests choosing a weaker ordering. After this change, it instead suggests the success ordering is not strong enough, and suggests chosing a stronger one. This is more likely to be correct. Also, before this change, the compiler suggested downgrading an invalid AcqRel failure ordering to Relaxed, without mentioning Acquire as an option.
-
由 bors 提交于
Rebase LLVM submodule This is a rebase of our LLVM fork onto LLVM 14.0.5, which is intended to be the last release of the 14.x series. Additionally: * I've dropped three patches that were needed to build on FreeBSD 11, which is no longer necessary after #97944. * I've dropped some cherry-picks that were later reverted. * I've cherry-picked https://github.com/llvm/llvm-project/commit/caa2a829cdf905a5e8664d96a464d414b2adb42e for https://github.com/rust-lang/rust/issues/96797 (fyi `@Amanieu)`
-
由 Ralf Jung 提交于
We now have an infallible function that also tells us which kind of allocation we are talking about. Also we do longer have to distinguish between data and function allocations for liveness.
-
由 Wilfred Hughes 提交于
"can not" should be "cannot", and add punctuation.
-