zig/stage1/config.zig.in

pub const have_llvm = true;
pub const llvm_has_m68k = false;
pub const llvm_has_csky = false;
pub const llvm_has_arc = false;
pub const llvm_has_xtensa = false;
pub const version: [:0]const u8 = "@RESOLVED_ZIG_VERSION@";
pub const semver = @import("std").SemanticVersion.parse(version) catch unreachable;
pub const enable_logging: bool = false;
pub const enable_link_snapshots: bool = false;
pub const enable_tracy = false;
pub const value_tracing = false;
pub const have_stage1 = false;
pub const skip_non_native = false;
pub const only_c = false;
pub const force_gpa = false;
pub const only_core_functionality = true;
enable the LLVM backend in stage2 This takes a bit longer since the interpreted part has to do more work but it saves a round trip through the compiler by allowing `zig2 build` to be the final step. 1-2-3, done. For me this is currently failing due to compilation errors generated by GCC when compiling zig2.c but in theory if those are fixed, it should work! 2022-11-16 06:04:18 +00:00			`pub const have_llvm = true;`
stage2: update LLVM backend to for LLVM 13 There was some new code in master branch enumerating all the targets and a new target was added so we needed to add the glue code. This commit also introduces some build options to support experimental LLVM targets. 2021-09-01 06:50:10 +01:00			`pub const llvm_has_m68k = false;`
			`pub const llvm_has_csky = false;`
			`pub const llvm_has_arc = false;`
update CPU features to LLVM 16 2023-01-26 23:33:40 +00:00			`pub const llvm_has_xtensa = false;`
cmake: Mark <root>/.git/HEAD as a configure dependency This ensures that the Zig version will be re-computed when jumping through the source tree, which is especially important if bisecting across AstGen- or other changes that must not use the old cache. 2022-10-31 20:12:52 +00:00			`pub const version: [:0]const u8 = "@RESOLVED_ZIG_VERSION@";`
add ast-check flag to zig fmt, fix found bugs 2021-06-13 20:27:27 +01:00			`pub const semver = @import("std").SemanticVersion.parse(version) catch unreachable;`
redo CMakeLists.txt to use WASI interpreter current status is that it hits error: OutOfMemory for unknown reasons, probably due to bugs in the C WASI interpreter port. 2022-11-15 07:33:05 +00:00			`pub const enable_logging: bool = false;`
macho: dump linker's state as JSON Each element of the output JSON has the VM address of the generated binary nondecreasing (some elements might occupy the same VM address for example the atom and the relocation might coincide in the address space). The generated JSON can be inspected manually or via a preview tool `zig-snapshots` that I am currently working on and will allow the user to inspect interactively the state of the linker together with the positioning of sections, symbols, atoms and relocations within each snapshot state, and in the future, between snapshots too. This should allow for quicker debugging of the linker which is nontrivial when run in the incremental mode. Note that the state will only be dumped if the compiler is built with `-Dlink-snapshot` flag on, and then the compiler is passed `--debug-link-snapshot` flag upon compiling a source/project. 2021-10-14 12:50:10 +01:00			`pub const enable_link_snapshots: bool = false;`
simplify `zig info` and rename it to `zig env` also add version to it 2020-08-18 01:06:23 +01:00			`pub const enable_tracy = false;`
stage2: use std.debug.Trace only when explicitly enabled Because it bumps up the stack space requirements, which is making a test case fail on aarch64 drone CI. 2022-06-09 23:33:04 +01:00			`pub const value_tracing = false;`
redo CMakeLists.txt to use WASI interpreter current status is that it hits error: OutOfMemory for unknown reasons, probably due to bugs in the C WASI interpreter port. 2022-11-15 07:33:05 +00:00			`pub const have_stage1 = false;`
stage2: wire up -Dskip-non-native The purpose of this is to save time in the edit-compile-test cycle when working on stage2 code. 2020-12-02 21:51:22 +00:00			`pub const skip_non_native = false;`
enable the LLVM backend in stage2 This takes a bit longer since the interpreted part has to do more work but it saves a round trip through the compiler by allowing `zig2 build` to be the final step. 1-2-3, done. For me this is currently failing due to compilation errors generated by GCC when compiling zig2.c but in theory if those are fixed, it should work! 2022-11-16 06:04:18 +00:00			`pub const only_c = false;`
interpret the WASI blob to produce zig2.c and compiler_rt.c * synchronize zig1.c from zig-wasi external project * change the way argv works to avoid absolute paths * autodetect isatty * compiler_rt: disable some functions when object format is C * add missing flag from config.zig.in The next problem is that compiling compiler_rt.c with gcc gives "conflicting types" errors for `__eqhf2` and friends. 2022-11-16 00:40:04 +00:00			`pub const force_gpa = false;`
rename omit_pkg_fetching_code to only_core_functionality No functional changes. This renames an internal build option to better reflect how it is used. 2023-05-18 00:00:24 +01:00			`pub const only_core_functionality = true;`