- 08 12月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-
- 26 10月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-
- 29 11月, 2016 1 次提交
-
-
由 Florian Diebold 提交于
-
- 01 9月, 2016 1 次提交
-
-
由 Michael Woerister 提交于
-
- 23 8月, 2016 1 次提交
-
-
由 Niko Matsakis 提交于
Fixes #35593
-
- 01 5月, 2016 1 次提交
-
-
由 James Miller 提交于
Coercion casts (`expr as T` where the type of `expr` can be coerced to `T`) are essentially no-ops, as the actual work is done by a coercion. Previously a check for type equality was used to avoid emitting the redundant cast in the MIR, but this failed for coercion casts of function items that had lifetime parameters. The MIR trans code doesn't handle `FnPtr -> FnPtr` casts and produced an error. Also fixes a bug with type ascription expressions not having any adjustments applied. Fixes #33295
-
- 09 4月, 2016 1 次提交
-
-
由 Jeffrey Seyfried 提交于
-
- 09 1月, 2016 1 次提交
-
-
由 Niko Matsakis 提交于
Fixes #29857. Fixes #30589.
-
- 19 2月, 2015 1 次提交
-
-
由 Björn Steinbrink 提交于
In `if loop {} {}`, the `if` is actually unreachable, but we didn't handle that correctly and when trying to translate the `if` we tried to branch on the "return value" of the loop expression, which is not an `i1` and therefore triggered an LLVM assertion.
-
- 17 2月, 2015 1 次提交
-
-
由 Manish Goregaokar 提交于
-
- 14 2月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
if found on the `main()` function. This lets you write tests that live in `compile-fail` but are expected to compile successfully. This is handy when you have many small variations on a theme that you want to keep together, and you are just testing the type checker, not the runtime semantics.
-
- 08 1月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
-
- 05 1月, 2015 1 次提交
-
-
由 Huon Wilson 提交于
-
- 02 1月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
Closes #17732 Closes #18819 Closes #19479 Closes #19631 Closes #19632 Closes #19850 Closes #19883 Closes #20005 Closes #20009 Closes #20389
-
- 25 8月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
The privacy pass of the compiler was previously not taking into account the privacy of foreign items, or bindings to external functions. This commit fixes this oversight by encoding the visibility of foreign items into the metadata for each crate. Any code relying on this will start to fail to compile and the bindings must be marked with `pub` to indicate that they can be used externally. Closes #16725 [breaking-change]
-
- 16 5月, 2014 1 次提交
-
-
由 Felix S. Klock II 提交于
Each test works by rendering the flowgraph for the last identified block we see in expanded pretty-printed output, and comparing it (via `diff`) against a checked in "foo.dot-expected.dot" file. Each test post-processes the output to remove NodeIds ` (id=NUM)` so that the expected output is somewhat stable (or at least independent of how we assign NodeIds) and easier for a human to interpret when looking at the expected output file itself. ---- Test writing style notes: I usually tried to write the tests in a way that would avoid duplicate labels in the output rendered flow graph, when possible. The tests that have string literals "unreachable" in the program text are deliberately written that way to remind the reader that the unreachable nodes in the resulting graph are not an error in the control flow computation, but rather a natural consequence of its construction.
-
- 07 4月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-
- 21 3月, 2014 2 次提交
-
-
由 Alex Crichton 提交于
-
由 Daniel Fagnan 提交于
Signed-off-by: NDaniel Fagnan <dnfagnan@gmail.com>
-
- 08 2月, 2014 1 次提交
-
-
由 Derek Guenther 提交于
-
- 23 12月, 2013 1 次提交
-
-
由 Andreas Neuhaus 提交于
-
- 13 12月, 2013 1 次提交
-
-
由 Jack Moffitt 提交于
-
- 30 11月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
This infrastructure is meant to support runnings tests that involve various interesting interdependencies about the types of crates being linked or possibly interacting with C libraries. The goal of these make tests is to not restrict them to a particular test runner, but allow each test to run its own tests. To this end, there is a new src/test/run-make directory which has sub-folders of tests. Each test requires a `Makefile`, and running the tests constitues simply running `make` inside the directory. The new target is `check-stageN-rmake`. These tests will have the destination directory (as TMPDIR) and the local rust compiler (as RUSTC) passed along to them. There is also some helpful cross-platform utilities included in src/test/run-make/tools.mk to aid with compiling C programs and running them. The impetus for adding this new test suite is to allow various interesting forms of testing rust linkage. All of the tests initially added are various flavors of compiling Rust and C with one another as well as just making sure that rust linkage works in general. Closes #10434
-