about summary refs log tree commit diff
path: root/src/test/ui/consts/miri_unleashed
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-1284/+0
2022-12-13Make some diagnostics not depend on the source of what they reference being ↵Oli Scherer-13/+2
available
2022-12-06Change CTFE backtraces to use `note` instead of `label` to preserve their orderOli Scherer-17/+32
labels are reordered within the file in which they are reported, which can mess up the stack trace
2022-12-06Remove now-redundant file/line info from const backtracesOli Scherer-7/+7
2022-12-01rustc_ast_lowering: Stop lowering imports into multiple itemsVadim Petrochenkov-2/+2
Lower them into a single item with multiple resolutions instead. This also allows to remove additional `NodId`s and `DefId`s related to those additional items.
2022-11-16cleanup and dedupe CTFE and Miri error reportingRalf Jung-8/+32
2022-10-08Split slice part of feature(half_open_range_patterns) to [...]_in_slicesUrgau-1/+1
2022-10-07make const_err a hard errorRalf Jung-494/+305
2022-10-01bless ui testsMaybe Waffle-26/+26
2022-09-24Note the type when unable to drop values in compile timeDeadbeef-3/+3
2022-09-09The `<*const T>::guaranteed_*` methods now return an option for the unknown caseOli Scherer-8/+4
2022-08-30Rollup merge of #101101 - RalfJung:read-pointer-as-bytes, r=oli-obkDylan DPC-0/+3
interpret: make read-pointer-as-bytes a CTFE-only error with extra information Next step in the reaction to https://github.com/rust-lang/rust/issues/99923. Also teaches Miri to implicitly strip provenance in more situations when transmuting pointers to integers, which fixes https://github.com/rust-lang/miri/issues/2456. Pointer-to-int transmutation during CTFE now produces a message like this: ``` = help: this code performed an operation that depends on the underlying bytes representing a pointer = help: the absolute address of a pointer is not known at compile-time, so such operations are not supported ``` r? ``@oli-obk``
2022-08-29Rollup merge of #101131 - RalfJung:ctfe-no-needs-rfc, r=oli-obkMatthias Krüger-2/+5
CTFE: exposing pointers and calling extern fn is just impossible The remaining "needs RFC" errors are just needlessly confusing, I think -- time to get rid of that error variant. They are anyway only reachable with miri-unleashed (if at all). r? `@oli-obk`
2022-08-28entirely get rid of NeedsRfc CTFE errorsRalf Jung-0/+3
2022-08-28CTFE: exposing pointers and calling extern fn doesn't need an RFC, it is ↵Ralf Jung-2/+2
just impossible
2022-08-27adjust testsRalf Jung-0/+3
2022-08-23extra sanity check against consts pointing to mutable memoryRalf Jung-8/+8
2022-07-26bless tests, remove nonexistent E0395Deadbeef-23/+6
2022-07-20make use of symbolic vtables in interpreterRalf Jung-4/+4
2022-07-01Shorten def_span for more items.Camille GILLOT-140/+70
2022-06-29interpret: adjust error from constructing an invalid valueRalf Jung-14/+14
2022-06-25bless remaining testsRalf Jung-0/+42
2022-06-25make const_err show up in future breakage reportsRalf Jung-0/+139
2022-06-05interpret: better control over whether we read data with provenance, and ↵Ralf Jung-1/+1
implicit provenance stripping where possible
2022-05-13Rustc changes for permissive provenancecarbotaniuman-2/+2
2022-03-07Update tests after feature stabilizationEric Holk-10/+0
2022-01-21Override rustc version in ui and mir-opt tests to get stable hashesThe 8472-2/+2
Building a dozen separate regexps for each test in compiletest consumes significant amounts of CPU cycles. Using `RUSTC_FORCE_INCR_COMP_ARTIFACT_HEADER` stabilizes hashes calcuated for the individual tests so no test-dependent normalization is needed. Hashes for the standard library still change so some normalizations are still needed.
2022-01-12Remove ui tests for LLVM-style inline assemblyTomasz Miąsko-29/+4
2021-12-20compare calling convention instead of call ABIRalf Jung-2/+2
2021-12-16Auto merge of #89836 - pierwill:fix-85142-crate-hash, r=wesleywiserbors-2/+2
Include rustc version in `rustc_span::StableCrateId` `rustc_span::def_id::StableCrateId` is a hash of various data about a crate during compilation. This PR includes the version of `rustc` in the input when computing this hash. From a cursory reading of [RFC 2603](https://rust-lang.github.io/rfcs/2603-rust-symbol-name-mangling-v0.html), this appears to be acceptable within that design. In order to pass the `mir-opt` and `ui` test suites, this adds new [normalization for hashes and symbol names in `compiletest`](https://github.com/rust-lang/rust/pull/89836/files#diff-03a0567fa80ca04ed5a55f9ac5c711b4f84659be2d0ac4a984196d581c04f76b). These are enabled by default, but we might prefer it to be configurable. In the UI tests, I had to truncate a significant amount of error annotations in v0 symbols (and maybe some legacy) in order to get the normalization to work correctly. (See https://github.com/rust-lang/rust/issues/90116.) Closes #85142.
2021-12-13Include rustc version in `rustc_span::StableCrateId`pierwill-2/+2
Normalize symbol hashes in compiletest. Remove DefId sorting
2021-12-12Stabilize asm! and global_asm!Amanieu d'Antras-5/+7
They are also removed from the prelude as per the decision in https://github.com/rust-lang/rust/issues/87228. stdarch and compiler-builtins are updated to work with the new, stable asm! and global_asm! macros.
2021-11-06Stabilize `const_raw_ptr_deref` for `*const T`Jacob Pratt-15/+0
This stabilizes dereferencing immutable raw pointers in const contexts. It does not stabilize `*mut T` dereferencing. This is placed behind the `const_raw_mut_ptr_deref` feature gate.
2021-10-15Bless testsCameron Steffen-4/+4
2021-10-04Stabilize `const_panic`Jacob Pratt-12/+0
2021-09-25Bless testsGary Guo-2/+2
2021-08-25Fix debugger stepping behavior around `match` expressionsWesley Wiser-4/+4
Previously, we would set up the source lines for `match` expressions so that the code generated to perform the test of the scrutinee was matched to the line of the arm that required the test and then jump from the arm block to the "next" block was matched to all of the lines in the `match` expression. While that makes sense, it has the side effect of causing strange stepping behavior in debuggers. I've changed the source information so that all of the generated tests are sourced to `match {scrutinee}` and the jumps are sourced to the last line of the block they are inside. This resolves the weird stepping behavior in all debuggers and resolves some instances of "ambiguous symbol" errors in WinDbg preventing the user from setting breakpoints at `match` expressions.
2021-08-15Fix ui tests for llvm_asm! deprecationAmanieu d'Antras-4/+5
2021-08-04Remove trailing whitespace from error messagesFabian Wolff-1/+1
2021-07-14test dynamic check for ptr-int-casts (unleashed)Ralf Jung-3/+21
2021-07-14adjust testsRalf Jung-17/+17
2021-07-06Revert "Revert "Update tests""bjorn3-2/+2
This reverts commit 715c68fe90c6f1d0b3004ad18f16e0811f209992.
2021-06-28Bless the test suite.Charles Lew-2/+2
2021-06-13update tests involving CTFE validationRémy Rakic-4/+4
2021-06-07Revert "Update tests"bjorn3-2/+2
This reverts commit c76b1b031753fc08a18a3906d828683476c1e595.
2021-05-30Update testsbjorn3-2/+2
2021-05-1532bit blessRalf Jung-38/+28
2021-05-15get rid of a bunch of unnecessary NOTE in const testsRalf Jung-59/+38
2021-05-12Show macro name in 'this error originates in macro' messageAaron Hill-4/+4
When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-03-31Add 32bit.stderr files.Hameer Abbasi-0/+295
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-05-19 00:32:11 +0000