summary refs log tree commit diff
path: root/src/test/run-pass
AgeCommit message (Collapse)AuthorLines
2019-04-02Permit unwinding through FFI by defaultMark Rousskov-0/+2
See #58794 for context.
2019-02-25Auto merge of #57367 - petrochenkov:unrestab, r=Centrilbors-2/+0
Stabilize `unrestricted_attribute_tokens` In accordance with a plan described in https://internals.rust-lang.org/t/unrestricted-attribute-tokens-feature-status/8561/3. Delimited non-macro non-builtin attributes now support the same syntax as macro attributes: ``` PATH PATH `(` TOKEN_STREAM `)` PATH `[` TOKEN_STREAM `]` PATH `{` TOKEN_STREAM `}` ``` Such attributes mostly serve as inert proc macro helpers or tool attributes. To some extent these attributes are de-facto stable due to a hole in feature gate checking (feature gating is done too late - after macro expansion.) So if macro *removes* such helper attributes during expansion (and it must remove them, unless it's a derive macro), then the code will work on stable. Key-value non-macro non-builtin attributes are now restricted to bare minimum required to support what we support on stable - unsuffixed literals (https://github.com/rust-lang/rust/issues/34981). ``` PATH `=` LITERAL ``` (Key-value macro attributes are not supported at all right now.) Crater run in https://github.com/rust-lang/rust/pull/57321 found no regressions for this change. There are multiple possible ways to extend key-value attributes (https://github.com/rust-lang/rust/pull/57321#issuecomment-451574065), but I'd expect an RFC for that and it's not a pressing enough issue to block stabilization of delimited attributes. Built-in attributes are still restricted to the "classic" meta-item syntax, nothing changes here. https://github.com/rust-lang/rust/pull/57321 goes further and adds some additional restrictions (more consistent input checking) to built-in attributes. Closes https://github.com/rust-lang/rust/issues/55208
2019-02-25Auto merge of #58302 - SimonSapin:tryfrom, r=alexcrichtonbors-4/+3
Stabilize TryFrom and TryInto with a convert::Infallible empty enum This is the plan proposed in https://github.com/rust-lang/rust/issues/33417#issuecomment-423073898
2019-02-25Stabilize `unrestricted_attribute_tokens`Vadim Petrochenkov-2/+0
2019-02-25Test that binop subtyping in rustc_typeck fixes #27949Jamie Turner-0/+41
2019-02-24Auto merge of #58304 - gnzlbg:simd_saturated, r=nagisabors-0/+92
Add generic simd saturated add/sub intrinsics r? @eddyb
2019-02-22Rollup merge of #58059 - RalfJung:before_exec, r=alexcrichtonMazdak Farrokhzad-83/+115
deprecate before_exec in favor of unsafe pre_exec Fixes https://github.com/rust-lang/rust/issues/39575 As per the [lang team decision](https://github.com/rust-lang/rust/issues/39575#issuecomment-442993358): > The language team agreed that before_exec should be unsafe, and leaves the details of a transition plan to the libs team. Cc @alexcrichton @rust-lang/libs how would you like to proceed?
2019-02-20Rollup merge of #58044 - Lokathor:lokathor, r=alexcrichtonkennytm-0/+12
Make overflowing and wrapping negation const Remember that the signed and unsigned versions are slightly different here, so there's four functions made const instead of just two.
2019-02-13Stabilize TryFrom and TryIntoSimon Sapin-2/+1
2019-02-13Use convert::Infallible instead of never in the blanket TryFrom implSimon Sapin-2/+2
2019-02-12Merging masterMatthias Einwag-21/+166
2019-02-12Auto merge of #58051 - SimonSapin:str_escape, r=alexcrichtonbors-3/+0
Stabilize str::escape_* methods with new return types… … that implement `Display` and `Iterator<Item=char>`, as proposed in FCP: https://github.com/rust-lang/rust/issues/27791#issuecomment-376864727
2019-02-12Auto merge of #58341 - alexreg:cosmetic-2-doc-comments, r=steveklabnikbors-7/+7
Cosmetic improvements to doc comments This has been factored out from https://github.com/rust-lang/rust/pull/58036 to only include changes to documentation comments (throughout the rustc codebase). r? @steveklabnik Once you're happy with this, maybe we could get it through with r=1, so it doesn't constantly get invalidated? (I'm not sure this will be an issue, but just in case...) Anyway, thanks for your advice so far!
2019-02-12Stabilize str::escape_* methodsSimon Sapin-3/+0
FCP: https://github.com/rust-lang/rust/issues/27791#issuecomment-376864727
2019-02-12Auto merge of #58246 - pmccarter:master, r=oli-obkbors-0/+34
Make `saturating_add` and `saturating_sub` `const` functions Fixes #58030
2019-02-11rename variable and add test directive for #58030Patrick McCarter-0/+1
2019-02-10tests: doc commentsAlexander Regueiro-7/+7
2019-02-10Auto merge of #58129 - RalfJung:maybe-uninit, r=cramertjbors-3/+3
MaybeUninit: some docs, rename into_inner -> into_initialized, return &mut from set
2019-02-09Auto merge of #57885 - arielb1:xform-probe, r=nikomatsakisbors-0/+59
Avoid committing to autoderef in object method probing This fixes the "leak" introduced in #57835 (see test for details, also apparently #54252 had no tests for the "leaks" that were fixed in it, so go ahead and add one). Maybe beta-nominating because regression, but I'm against landing things on beta we don't have to. r? @nikomatsakis
2019-02-08Remove trailing white-spacegnzlbg-1/+1
2019-02-08simd-saturating-arith test requires LLVM >= 8.0gnzlbg-3/+3
2019-02-08Add simd_saturating_{add,sub} intrinsicsgnzlbg-0/+92
2019-02-07fix existing testsmark-8/+8
2019-02-07Refactor const saturating intrinsics emulation and add unstable feature ↵Patrick McCarter-0/+2
attribute #58030
2019-02-06Change RawWaker constructor to const fnMatthias Einwag-8/+2
2019-02-06fix saturating_sub() underflow for unsigned ints #58030Patrick McCarter-0/+4
2019-02-06Allow const assignment for int saturating_sub() for #58030Patrick McCarter-1/+15
2019-02-05Move ArcWake in common test file.Matthias Einwag-110/+73
2019-02-05fix test caseRalf Jung-3/+3
2019-02-05Allow const assignment for int saturating_add() calls for #58030Patrick McCarter-0/+13
2019-02-03Fix testMatthias Einwag-1/+1
2019-02-03Apply review suggestions and fix testsMatthias Einwag-42/+130
2019-02-02rustfmt the testRalf Jung-30/+62
2019-02-01fix the build errorsLokathor-3/+6
2019-02-01const-int-wrapping.rs += wrapping_negLokathor-2/+5
2019-02-01const-int-overflowing.rs += overflowing_negLokathor-0/+6
2019-02-01update testRalf Jung-13/+13
2019-01-31Add more tests for #[repr(align(x))] on enumsNiklas Fiekas-4/+42
2019-01-30Allow #[repr(align(x))] on enums (#57996)Niklas Fiekas-0/+17
2019-01-29avoid committing to autoderef in object method probingAriel Ben-Yehuda-0/+59
2019-01-27Mark non-static generators as always UnpinWim Looman-1/+19
2019-01-27impl Generator for Pin<Box<Generator>>Wim Looman-0/+13
2019-01-27Change generator trait to use pinningWim Looman-51/+66
2019-01-27Auto merge of #57765 - Mark-Simulacrum:bootstrap-bump, r=alexcrichtonbors-29/+27
Bump bootstrap compiler to 1.33 beta r? @alexcrichton or @pietroalbini cc @rust-lang/release
2019-01-26Replace deprecated ATOMIC_INIT constsMark Rousskov-29/+27
2019-01-26Rollup merge of #57827 - parched:ignore, r=nikomatsakisMazdak Farrokhzad-0/+1
Ignore aarch64 in simd-intrinsic-generic-reduction This fails on AArch64 see https://github.com/rust-lang/rust/issues/54510 Disabling it for now until it's fixed/implemented in LLVM cc @gnzlbg
2019-01-24Auto merge of #57269 - gnzlbg:simd_bitmask, r=rkruppebors-0/+61
Add intrinsic to create an integer bitmask from a vector mask This PR adds a new simd intrinsic: `simd_bitmask(vector) -> unsigned integer` that creates an integer bitmask from a vector mask by extracting one bit of each vector lane. This is required to implement: https://github.com/rust-lang-nursery/packed_simd/issues/166 . EDIT: the reason we need an intrinsics for this is that we have to truncate the vector lanes to an `<i1 x N>` vector, and then bitcast that to an `iN` integer (while making sure that we only materialize `i8`, ... , `i64` - that is, no `i1`, `i2`, `i4`, types), and we can't do any of that in a Rust library. r? @rkruppe
2019-01-22Add intrinsic to create an integer bitmask from the MSB of integer vectorsgnzlbg-0/+61
2019-01-22Ignore aarch64 in simd-intrinsic-generic-reductionJames Duley-0/+1
This fails on AArch64 see https://github.com/rust-lang/rust/issues/54510
2019-01-21Rollup merge of #56796 - KrishnaSannasi:try_from_impl_change, r=shepmasterMazdak Farrokhzad-0/+37
Change bounds on `TryFrom` blanket impl to use `Into` instead of `From` This is from this [comment](https://github.com/rust-lang/rust/issues/33417#issuecomment-447111156) I made. This will expand the impls available for `TryFrom` and `TryInto`, without losing anything in the process.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 00:05:08 +0000