| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-07-27 | tests: Move run-pass tests without naming conflicts to ui | Vadim Petrochenkov | -19/+0 | |
| 2019-07-27 | tests: Add missing run-pass annotations | Vadim Petrochenkov | -0/+1 | |
| 2019-05-16 | Added ignore-sgx for appropriate tests | Dario Gonzalez | -0/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-07-09 | bump minimum LLVM version to 5.0 | gnzlbg | -1/+0 | |
| 2018-06-04 | test: Ignore some problematic tests on sparc and sparc64 | John Paul Adrian Glaubitz | -0/+2 | |
| 2018-03-29 | Ignore stack-probes tests on powerpc/s390x too | Josh Stone | -0/+2 | |
| We only support stack probes on x86 and x86_64. Other arches are already ignored. | ||||
| 2018-03-09 | test: ignore stack probe tests on mips* | James Cowgill | -0/+2 | |
| 2018-01-31 | Enable stack-probe tests with system LLVM >= 5.0 | Josh Stone | -1/+1 | |
| 2018-01-02 | Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI. | Ed Schouten | -0/+1 | |
| It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically. | ||||
| 2017-10-17 | test: Update Emscripten failures/passing | Alex Crichton | -1/+1 | |
| All tests should now have annotation for *why* they're ignored on emscripten. A few tests no longer need such an annotation as well! Closes #41299 | ||||
| 2017-07-21 | Ignore stack probe tests on AArch64 | Mátyás Mustoha | -0/+1 | |
| 2017-07-06 | rustc: Implement stack probes for x86 | Alex Crichton | -0/+20 | |
| This commit implements stack probes on x86/x86_64 using the freshly landed support upstream in LLVM. The purpose of stack probes here are to guarantee a segfault on stack overflow rather than having a chance of running over the guard page already present on all threads by accident. At this time there's no support for any other architecture because LLVM itself does not have support for other architectures. | ||||
