summary refs log tree commit diff
path: root/src/test/run-make/graphviz-flowgraph/Makefile
AgeCommit message (Collapse)AuthorLines
2015-01-20rustc: Remove deprecated flagsAlex Crichton-1/+1
This commit removes a number of deprecated flags from the compiler: * opt-level => -C opt-level * debuginfo => -C debuginfo * print-crate-name => --print crate-name * print-file-name => --print file-names * no-trans => -Z no-trans * no-analysis => -Z no-analysis * parse-only => -Z parse-only * dep-info => --emit dep-info This commit also moves the --pretty flag behind `-Z unstable-options` as the pretty printer will likely not be stable for 1.0 cc #19051
2015-01-13graphviz-flowgraph tests: use new `--xpretty flowgraph,unlabelled` option.Felix S. Klock II-1/+1
This makes the tests much easier to maintain; the particular details of the labels attached to exiting scopes is not worth the effort required to keep it up to date as things change in the compiler internals.
2014-12-22fix run-make/ tests now flowgraph printing has moved to the unstable ↵Felix S. Klock II-1/+1
`--xpretty` option.
2014-06-18Regression tests for flowgraph construction bug on ExprWhile.Felix S. Klock II-1/+2
2014-05-15Unit tests for flowgraph pretty printing.Felix S. Klock II-0/+37
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.