2020-08-21 08:25:09 +08:00
|
|
|
const std = @import("std");
|
avoid calling into stage1 backend when AstGen fails
The motivation for this commit is that there exists source files which
produce ast-check errors, but crash stage1 or otherwise trigger stage1
bugs. Previously to this commit, Zig would run AstGen, collect the
compile errors, run stage1, report stage1 compile errors and exit if
any, and then report AstGen compile errors.
The main change in this commit is to report AstGen errors prior to
invoking stage1, and in fact if any AstGen errors occur, do not invoke
stage1 at all.
This caused most of the compile error tests to fail due to things such
as unused local variables and mismatched stage1/stage2 error messages.
It was taking a long time to update the test cases one-by-one, so I
took this opportunity to unify the stage1 and stage2 testing harness,
specifically with regards to compile errors. In this way we can start
keeping track of which tests pass for 1, 2, or both.
`zig build test-compile-errors` no longer works; it is now integrated
into `zig build test-stage2`.
This is one step closer to executing compile error tests in parallel; in
fact the ThreadPool object is already in scope.
There are some cases where the stage1 compile errors were actually
better; those are left failing in this commit, to be addressed in a
follow-up commit.
Other changes in this commit:
* build.zig: improve support for -Dstage1 used with the test step.
* AstGen: minor cosmetic changes to error messages.
* stage2: add -fstage1 and -fno-stage1 flags. This now allows one to
download a binary of the zig compiler and use the llvm backend of
self-hosted. This was also needed for hooking up the test harness.
However, I realized that stage1 calls exit() and also has memory
leaks, so had to complicate the test harness by not using this flag
after all and instead invoking as a child process.
- These CLI flags will disappear once we start shipping the
self-hosted compiler as the main compiler. Until then, they can be
used to try out the work-in-progress stage2.
* stage2: select the LLVM backend by default for release modes, as long
as the target architecture is supported by LLVM.
* test harness: support setting the optimize mode
2021-07-01 02:27:39 +08:00
|
|
|
const TestContext = @import("../src/test.zig").TestContext;
|
2019-11-24 04:56:05 +08:00
|
|
|
|
|
|
|
|
pub fn addCases(ctx: *TestContext) !void {
|
2021-11-20 05:41:10 +08:00
|
|
|
try @import("compile_errors.zig").addCases(ctx);
|
|
|
|
|
try @import("stage2/cbe.zig").addCases(ctx);
|
2022-03-14 15:06:24 +08:00
|
|
|
// https://github.com/ziglang/zig/issues/10968
|
|
|
|
|
//try @import("stage2/nvptx.zig").addCases(ctx);
|
2019-11-24 04:56:05 +08:00
|
|
|
}
|
