Andrew Kelley 48c7e6c48b std.Target.CpuFeatures is now a struct with both CPU and feature set ... Previously it was a tagged union which was one of: * baseline * a specific CPU * a set of features Now, it's possible to have a CPU but also modify the CPU's feature set on top of that. This is closer to what LLVM does. This is more correct because Zig's notion of CPUs (and LLVM's) is not exact CPU models. For example "skylake" is not one very specific model; there are several different pieces of hardware that match "skylake" that have different feature sets enabled.		2020-01-22 17:13:31 -05:00
..
src	test harness: show annotated case name when translate-c test fails	2020-01-07 13:40:17 -05:00
stage1	enable native CPU feature for windows; disable failing tests	2020-01-21 21:46:06 -05:00
stage2
standalone	zig fmt and update extern fn to callconv(.C)	2020-01-06 15:34:50 -05:00
assemble_and_link.zig
cli.zig
compare_output.zig	avoid trying to translate microsoft's stdio.h inline functions	2020-01-01 20:33:07 -05:00
compile_errors.zig	std.Target.CpuFeatures is now a struct with both CPU and feature set	2020-01-22 17:13:31 -05:00
gen_h.zig
run_translated_c.zig	Handle forward-declared functions	2020-01-10 16:34:40 -05:00
runtime_safety.zig	fix safety for sentinel-slicing floats	2019-12-20 18:28:59 -05:00
stack_traces.zig
standalone.zig
tests.zig	std.Target.CpuFeatures is now a struct with both CPU and feature set	2020-01-22 17:13:31 -05:00
translate_c.zig	std.Target.CpuFeatures is now a struct with both CPU and feature set	2020-01-22 17:13:31 -05:00