d44c9bdbd9
ir: elemptr and add instructions
2020-04-26 01:20:58 -04:00
24a01eed90
basics of writing ELF and machine code generation
2020-04-23 16:41:20 -04:00
d58233b361
ir: improve ZIR emission enough to emit hello world
2020-04-22 03:08:50 -04:00
993e654554
emit zir skeleton
2020-04-22 00:04:52 -04:00
2e6ccec100
ir: analyze asm instruction
2020-04-21 22:19:32 -04:00
8d3e4147d5
ir: analyze deref instruction
2020-04-21 21:33:55 -04:00
2c11acf807
ir: analyze fieldptr instruction
2020-04-21 21:14:56 -04:00
2cdbb5f472
ir: analyze int casting
2020-04-21 19:48:59 -04:00
0746028a2a
ir: analyze int instruction
2020-04-21 17:54:00 -04:00
8671e8d6d4
ir: analyze fntype instruction
2020-04-21 17:06:09 -04:00
22e7ca5613
ir: analysis of fn instruction
2020-04-21 16:06:15 -04:00
8e0bcaca9b
ir: analyze str instruction
2020-04-21 01:20:01 -04:00
4c7507cceb
ir: semantic analysis skeleton
2020-04-21 00:56:30 -04:00
e74c5a7c24
ir: nice rendering of string literal constants
2020-04-19 20:44:18 -04:00
ded6e0326d
ir: rendering skeleton
2020-04-19 20:04:11 -04:00
7127c07f68
ir: parse types
2020-04-19 19:31:50 -04:00
018daa028e
rework types and values data layout
2020-04-19 19:31:50 -04:00
bd4280decf
beginnings of zig ir parser
2020-04-19 19:31:50 -04:00
2e806682f4
(breaking) std.Buffer => std.ArrayListSentineled(u8, 0)
...
This new name (and the fact that it is a function returning a type) will
make it more clear which use cases are better suited for ArrayList and
which are better suited for ArrayListSentineled.
Also for consistency with ArrayList,
* `append` => `appendSlice`
* `appendByte` => `append`
Thanks daurnimator for pointing out the confusion of std.Buffer.
2020-04-01 13:30:07 -04:00
9e7ae06249
std lib API deprecations for the upcoming 0.6.0 release
...
See #3811
2020-03-30 14:23:22 -04:00
fe4963412f
update self-hosted compiler to new format API
2019-12-08 23:17:03 -05:00
128034481a
solve recursion in self hosted
2019-11-26 18:25:29 +02:00
36849d8a7b
fixes and cleanup in self hosted
2019-11-26 11:52:12 +02:00
34b1ebefaa
Merge remote-tracking branch 'origin/master' into null-terminated-pointers
2019-11-24 20:28:46 -05:00
47f06be369
string literals are now null terminated
...
this also deletes C string literals from the language, and then makes
the std lib changes and compiler changes necessary to get the behavior
tests and std lib tests passing again.
2019-11-21 20:43:41 -05:00
c6076a1360
self hosted compiler: use enum literals
2019-11-07 10:30:56 +02:00
cb20093614
self hosted compiler: remove await async pattern
2019-11-07 10:30:11 +02:00
ed41d10a06
std: existing LinkedList is actually a TailQueue
2019-06-10 15:41:40 +10:00
b735764898
different array literal syntax when inferring the size
...
old syntax: []i32{1, 2, 3}
new syntax: [_]i32{1, 2, 3}
closes #1797
2019-06-09 19:26:32 -04:00
78af62a19a
Pack big.Int sign and length fields
...
This effectively takes one-bit from the length field and uses it as the
sign bit. It reduces the size of an Int from 40 bits to 32 bits on a
64-bit arch.
This also reduces std.Rational from 80 bits to 64 bits.
2019-04-11 19:36:35 +12:00
e025c70166
stage2: fix llvm.zig with opaque types back to single-item pointer
2019-02-14 23:17:11 -05:00
6769183a9d
fix implicit cast error unions with non-optional to optional pointer
...
and update self hosted compiler for C pointers
See #1059
2019-02-14 15:48:28 -05:00
dfbc063f79
`std.mem.Allocator.create` replaced with better API
...
`std.mem.Allocator.createOne` is renamed to `std.mem.Allocator.create`.
The problem with the previous API is that even after copy elision,
the initalization value passed as a parameter would always be a copy.
With the new API, once copy elision is done, initialization
functions can directly initialize allocated memory in place.
Related:
* #1872
* #1873
2019-02-03 16:13:28 -05:00
8139c5a516
New Zig formal grammar ( #1685 )
...
Reverted #1628 and changed the grammar+parser of the language to not allow certain expr where types are expected
2018-11-13 05:08:37 -08:00
378d3e4403
Solve the return type ambiguity ( #1628 )
...
Changed container and initializer syntax
* <container> { ... } -> <container> . { ... }
* <exrp> { ... } -> <expr> . { ...}
2018-10-15 09:51:15 -04:00
adefd1a52b
self-hosted: function calling another function
2018-07-24 20:24:05 -04:00
93e78ee722
self-hosted can compile libc hello world
2018-07-22 23:28:53 -04:00
f5a67dba08
self-hosted: implicit cast comptime ints to other ints
...
we now have successful exit codes from main linking
against libc
2018-07-20 01:46:49 -04:00
3908b4fdee
self-hosted: refactor ParsedFile out of existence
...
also we are successfully analyzing the return type of main
2018-07-19 15:11:39 -04:00
1d85b588ea
self-hosted: progress on IR for supporting libc hello world
...
* add c int types
* some more ir stubs
2018-07-19 00:08:47 -04:00
97bfeac13f
self-hosted: create tmp dir for .o files and emit .o file for fn
2018-07-16 20:52:50 -04:00
363f4facea
self-hosted: generate LLVM IR for simple function
2018-07-15 00:07:33 -04:00
28c3d4809b
rename Module to Compilation
...
and CompilationUnit to ObjectFile
2018-07-14 16:31:17 -04:00
278829fc2c
self-hosted: adding a fn to an llvm module
2018-07-14 16:03:22 -04:00
e78b1b810f
self-hosted: basic IR pass2
2018-07-13 21:56:38 -04:00
687bd92f9c
self-hosted: generate zig IR for simple function
...
no tests for this yet. I think the quickest path to testing will be
creating the .o files and linking with libc, executing, and then
comparing output.
2018-07-12 15:12:44 -04:00
Andrew Kelley
Vexu
daurnimator
Marc Tiehuis
Jimmi Holst Christensen
Andrew Kelley