summary refs log tree commit diff
path: root/src/test
AgeCommit message (Collapse)AuthorLines
2017-01-19disable run-pass/backtrace for openbsdSébastien Marie-0/+1
the backtrace test doesn't work on openbsd as it doesn't have support for libbacktrace without using filename.
2017-01-19more complete error messageNiko Matsakis-1/+1
2017-01-19only consider value items when searching for methods, not typesNiko Matsakis-0/+15
2017-01-17fix function arguments in constant promotionAriel Ben-Yehuda-0/+7
we can't create the target block until *after* we promote the arguments - otherwise the arguments will be promoted into the target block. oops. Fixes #38985.
2017-01-17Improve the warning cycle for `use $crate;`.Jeffrey Seyfried-3/+10
2017-01-07Merge pull request #38884 from nikomatsakis/beta-unmergedAlex Crichton-0/+169
More beta backports
2017-01-06Don't `unused_qualifications`-check global paths.Jeffrey Seyfried-4/+5
2017-01-06Add regression test.Jeffrey Seyfried-0/+43
2017-01-06Fix tidy warningJonathan Turner-0/+10
2017-01-06Add in test for E0090Jonathan Turner-0/+5
2017-01-06Fix ICE on i686 when calling immediate() on OperandValue::Ref in returnMark Simulacrum-0/+21
2017-01-06std: Don't pass overlapped handles to processesAlex Crichton-0/+90
This commit fixes a mistake introduced in #31618 where overlapped handles were leaked to child processes on Windows. On Windows once a handle is in overlapped mode it should always have I/O executed with an instance of `OVERLAPPED`. Most child processes, however, are not prepared to have their stdio handles in overlapped mode as they don't use `OVERLAPPED` on reads/writes to the handle. Now we haven't had any odd behavior in Rust up to this point, and the original bug was introduced almost a year ago. I believe this is because it turns out that if you *don't* pass an `OVERLAPPED` then the system will [supply one for you][link]. In this case everything will go awry if you concurrently operate on the handle. In Rust, however, the stdio handles are always locked, and there's no way to not use them unlocked in libstd. Due to that change we've always had synchronized access to these handles, which means that Rust programs typically "just work". Conversely, though, this commit fixes the test case included, which exhibits behavior that other programs Rust spawns may attempt to execute. Namely, the stdio handles may be concurrently used and having them in overlapped mode wreaks havoc. [link]: https://blogs.msdn.microsoft.com/oldnewthing/20121012-00/?p=6343 Closes #38811
2017-01-06rustc: Stabilize the `proc_macro` featureAlex Crichton-155/+1
This commit stabilizes the `proc_macro` and `proc_macro_lib` features in the compiler to stabilize the "Macros 1.1" feature of the language. Many more details can be found on the tracking issue, #35900. Closes #35900
2017-01-06Add test.Without Boats-0/+16
2017-01-06Fix rustdoc ICE.Jeffrey Seyfried-0/+57
2017-01-06Don't leak the compiler's internal representation of scopes in error messages.Eduard-Mihai Burtescu-0/+58
2017-01-06Regression test and exploratory unit test.Felix S. Klock II-0/+249
2017-01-06Style fixesJosh Driver-2/+1
2017-01-06Stop macro calls in structs for proc_macro_derive from panicingJosh Driver-0/+53
2017-01-06Fix regression with duplicate `#[macro_export] macro_rules!`.Jeffrey Seyfried-0/+35
2017-01-06fix promotion of MIR terminatorsAriel Ben-Yehuda-0/+20
promotion of MIR terminators used to try to promote the destination it is trying to promote, leading to stack overflow. Fixes #37991.
2016-12-30Demote most backwards incompatible ambiguity errors from RFC 1560 to warnings.Jeffrey Seyfried-0/+30
2016-12-30Disable field reorderingAustin Hicks-36/+32
2016-12-30Fix non-termination in `resolve`.Jeffrey Seyfried-1/+3
2016-12-30clear discriminant drop flag at the bottom of a ladderAriel Ben-Yehuda-0/+54
Fixes #38437.
2016-12-29Remove --crate-type=metadata from betaNick Cameron-207/+0
Leaves most of the implementation, just ignores the argument itself.
2016-12-19Auto merge of #38140 - jseyfried:proc_macro_visibility, r=nrcbors-1/+6
Require `#[proc_macro_derive]` functions to be `pub` r? @nrc
2016-12-18Auto merge of #38051 - sanxiyn:unused-type-alias-3, r=eddybbors-0/+22
Warn unused type aliases, reimplemented Reimplementation of #37631. Fix #37455.
2016-12-18Auto merge of #37429 - camlorn:univariant_layout_optimization, r=eddybbors-53/+130
struct field reordering and optimization This is work in progress. The goal is to divorce the order of fields in source code from the order of fields in the LLVM IR, then optimize structs (and tuples/enum variants)by always ordering fields from least to most aligned. It does not work yet. I intend to check compiler memory usage as a benchmark, and a crater run will probably be required. I don't know enough of the compiler to complete this work unaided. If you see places that still need updating, please mention them. The only one I know of currently is debuginfo, which I'm putting off intentionally until a bit later. r? @eddyb
2016-12-17Auto merge of #38279 - KalitaAlexey:issue-8521, r=jseyfriedbors-0/+64
macros: allow a `path` fragment to be parsed as a type parameter bound Allow a `path` fragment to be parsed as a type parameter bound. Fixes #8521.
2016-12-17Auto merge of #38205 - jseyfried:fix_module_directory_regression, r=eddybbors-0/+33
macros: fix the expected paths for a non-inline module matched by an `item` fragment Fixes #38190. r? @nrc
2016-12-16Allow path fragments to be parsed as type parameter bounds in macro expansionKalita Alexey-0/+64
2016-12-15Warn unused type aliasesSeo Sanghyeon-0/+22
2016-12-15Require `#[proc_macro_derive]` functions to be `pub`.Jeffrey Seyfried-1/+6
2016-12-15Fix regression in resolution of primitive typesVadim Petrochenkov-0/+20
2016-12-14Add a case to type-sizes to explicitly verify that field reordering triggers.Austin Hicks-0/+7
2016-12-14Fix computation of enum names based off the discrfield in the case of the ↵Austin Hicks-2/+2
null pointer optimization. This functionality is needed by pretty printers for gdb and lldb.
2016-12-14Fix -Z print-type-sizes and tests.Austin Hicks-32/+29
This was done by sorting the fields by increasing offset; as a consequence, the order of -Z print-type-sizes matches memory order not source order.
2016-12-14Incorporate review commentsAustin Hicks-2/+1
2016-12-14Make tidyAustin Hicks-1/+1
2016-12-14Fix closure arguments which are immediate because of field reordering.Austin Hicks-0/+22
While building immediates goes through type_of::type_of, extracting them must account for field reorderings.
2016-12-14Fix having multiple reprs on the same type.Austin Hicks-1/+45
This bug has applied to master for an indefinite period of time and is orthogonal to univariant layout optimization.
2016-12-14Change how type-sizes works slightly: we want to ensure that [i16; 0] ↵Austin Hicks-1/+2
introduces padding
2016-12-14Fix type-sizes testAustin Hicks-1/+1
2016-12-14Make tidyAustin Hicks-2/+2
2016-12-14Modify debuginfo to deal with the difference between source and memory orderAustin Hicks-17/+17
Fix gdb enum tests to ignore garbage variants, as we no longer actually know what the garbage is.
2016-12-14Add yet more missing #[repr(C)] to testsAustin Hicks-0/+2
2016-12-14Fix extern-pass-empty test, which needed repr(C)Austin Hicks-0/+3
2016-12-14Make constant field access account for field reordering.Austin Hicks-3/+1
2016-12-14Fix bugs to optimizing enums:Austin Hicks-2/+6
- The discriminant must be first in all variants. - The loop responsible for patching enum variants when the discriminant is enlarged was nonfunctional.