os: disable unexpected error tracing on stage 2 builds

The self-hosted compiler cannot yet deal with the print function that this
field enables. It is not critical, however, and allows us to remove formatting
from the list of neccesary features to implement to get the page allocator
working.
This commit is contained in:
Robin Voetter 2021-12-18 00:57:23 +01:00
parent 138f85bf25
commit 28bcd7dbdd

View File

@ -4968,7 +4968,11 @@ pub fn toPosixPath(file_path: []const u8) ![MAX_PATH_BYTES - 1:0]u8 {
/// if this happens the fix is to add the error code to the corresponding /// if this happens the fix is to add the error code to the corresponding
/// switch expression, possibly introduce a new error in the error set, and /// switch expression, possibly introduce a new error in the error set, and
/// send a patch to Zig. /// send a patch to Zig.
pub const unexpected_error_tracing = builtin.mode == .Debug; /// The self-hosted compiler is not fully capable of handle the related code.
/// Until then, unexpected error tracing is disabled for the self-hosted compiler.
/// TODO remove this once self-hosted is capable enough to handle printing and
/// stack trace dumping.
pub const unexpected_error_tracing = !builtin.zig_is_stage2 and builtin.mode == .Debug;
pub const UnexpectedError = error{ pub const UnexpectedError = error{
/// The Operating System returned an undocumented error code. /// The Operating System returned an undocumented error code.