2015-08-05 16:22:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-10 15:39:52 -05:00
|
|
|
|
2015-08-05 20:26:58 -07:00
|
|
|
|
2015-11-23 22:47:25 -07:00
|
|
|
|
2018-09-10 17:30:45 -04:00
|
|
|
|
2017-01-10 15:39:52 -05:00
|
|
|
|
2015-12-03 00:47:35 -07:00
|
|
|
|
2017-01-10 15:39:52 -05:00
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2015-08-05 20:26:58 -07:00
|
|
|
|
2015-08-05 16:22:21 -07:00
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-16 00:42:56 -05:00
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
|
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
2019-02-24 12:53:28 -05:00
|
|
|
|
2019-02-16 00:42:56 -05:00
|
|
|
|
2018-09-09 23:58:52 -04:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2019-03-31 16:48:33 -04:00
|
|
|
|
2017-11-24 14:56:05 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-08-20 04:25:42 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-02-19 12:07:56 -05:00
|
|
|
|
|
|
|
|
|
2019-05-27 20:59:19 -04:00
|
|
|
|
|
|
|
|
|
2018-06-17 02:57:07 -04:00
|
|
|
|
2019-05-02 00:40:09 +09:00
|
|
|
|
|
|
|
|
|
2018-09-11 22:46:22 -04:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2019-03-02 10:38:27 -05:00
|
|
|
|
2017-05-02 17:34:21 -04:00
|
|
|
|
|
|
|
|
|
2018-04-16 03:26:10 +03:00
|
|
|
|
2019-02-01 17:49:29 -05:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2016-02-08 00:50:51 -07:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
|
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
2019-02-06 14:32:20 -05:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2019-05-08 20:49:07 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2018-02-04 22:06:03 -05:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2018-12-26 15:25:54 -05:00
|
|
|
|
|
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-04-19 15:38:12 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
2015-08-05 16:22:21 -07:00
|
|
|
|
2019-02-16 00:42:56 -05:00
|
|
|
|
2015-08-05 16:22:21 -07:00
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
2016-02-11 01:33:27 -07:00
|
|
|
|
|
|
|
|
|
2016-02-10 16:35:07 -07:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
2016-09-15 14:05:15 -04:00
|
|
|
|
|
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 15:54:08 -05:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-15 14:05:15 -04:00
|
|
|
|
|
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
2016-02-11 01:33:27 -07:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
2019-03-19 15:04:29 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-08-20 04:25:42 -04:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2015-11-30 19:58:53 -07:00
|
|
|
|
2015-08-05 16:22:21 -07:00
|
|
|
|
2017-04-30 18:56:24 -04:00
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-28 10:11:32 -05:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-28 15:40:57 -05:00
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
2019-02-28 10:11:32 -05:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-24 12:53:28 -05:00
|
|
|
|
|
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-12-26 19:44:08 -05:00
|
|
|
|
2018-01-04 22:46:26 -05:00
|
|
|
|
2018-01-03 19:39:04 -05:00
|
|
|
|
|
|
|
|
|
2018-01-03 21:32:50 -05:00
|
|
|
|
2018-01-03 19:39:04 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-04 22:46:26 -05:00
|
|
|
|
|
|
|
|
|
2017-12-26 19:44:08 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-24 15:30:30 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-24 12:53:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-09 23:58:52 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-09 18:07:11 -04:00
|
|
|
|
2018-09-09 23:58:52 -04:00
|
|
|
|
|
|
|
|
|
2018-09-09 18:07:11 -04:00
|
|
|
|
|
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-09 19:16:51 -05:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-09 19:16:51 -05:00
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-17 15:56:06 -07:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-11-04 02:09:33 +13:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
2017-09-18 21:06:53 -04:00
|
|
|
|
2017-09-30 16:59:31 -04:00
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2016-01-31 18:32:07 -07:00
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
2018-02-04 22:06:03 -05:00
|
|
|
|
2016-09-18 21:28:06 -04:00
|
|
|
|
2019-03-13 23:15:34 -04:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-03 12:34:20 -05:00
|
|
|
|
2017-03-13 11:54:56 -04:00
|
|
|
|
2017-03-13 13:11:55 -04:00
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2017-04-19 15:38:12 -04:00
|
|
|
|
|
|
|
|
|
2017-04-21 01:56:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-25 12:29:25 -04:00
|
|
|
|
2018-09-12 11:49:46 -04:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2017-05-02 17:34:21 -04:00
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2018-11-02 00:07:43 -04:00
|
|
|
|
2018-12-26 15:25:54 -05:00
|
|
|
|
2019-04-14 11:00:37 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-05-08 20:49:07 -04:00
|
|
|
|
2019-02-06 14:32:20 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2019-03-02 10:38:27 -05:00
|
|
|
|
2019-02-19 12:07:56 -05:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2019-05-27 20:59:19 -04:00
|
|
|
|
2015-11-30 19:58:53 -07:00
|
|
|
|
2019-03-06 13:22:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2018-09-28 16:41:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
|
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
2017-04-28 02:22:12 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-28 02:22:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
2017-10-01 15:51:55 -04:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2017-10-01 15:51:55 -04:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2018-09-04 22:18:04 -04:00
|
|
|
|
|
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-12 11:49:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-30 18:56:24 -04:00
|
|
|
|
2019-03-04 22:15:53 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2019-03-04 22:15:53 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
2018-09-04 22:18:04 -04:00
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-19 04:36:48 -04:00
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
2018-02-07 23:45:20 +01:00
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
2018-02-07 23:45:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-17 17:08:56 -04:00
|
|
|
|
2018-02-07 23:45:20 +01:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2018-02-07 23:45:20 +01:00
|
|
|
|
|
|
|
|
|
2017-04-11 06:14:46 -04:00
|
|
|
|
|
|
|
|
|
2019-02-28 10:11:32 -05:00
|
|
|
|
2019-02-28 15:40:57 -05:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2018-01-19 03:03:20 -05:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-16 00:42:56 -05:00
|
|
|
|
2019-04-26 20:41:37 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2016-01-27 19:22:58 -07:00
|
|
|
|
2019-03-31 16:48:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-02 17:34:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-16 03:26:10 +03:00
|
|
|
|
|
|
|
|
|
2019-02-16 00:42:56 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2015-11-24 22:32:26 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
|
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-18 21:06:53 -04:00
|
|
|
|
|
|
|
|
|
2017-09-30 16:59:31 -04:00
|
|
|
|
|
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
|
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
2017-03-13 13:11:55 -04:00
|
|
|
|
|
|
|
|
|
2018-09-11 22:46:22 -04:00
|
|
|
|
2017-04-25 12:29:25 -04:00
|
|
|
|
2019-02-19 12:07:56 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-02 00:40:09 +09:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2019-05-02 00:40:09 +09:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2019-05-27 20:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-02 00:07:43 -04:00
|
|
|
|
|
|
|
|
|
2019-02-01 17:49:29 -05:00
|
|
|
|
2019-04-14 11:00:37 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
2019-05-08 20:49:07 -04:00
|
|
|
|
|
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
2017-03-13 11:54:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
2015-12-01 01:06:10 -07:00
|
|
|
|
|
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2015-12-01 01:06:10 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2015-12-01 01:06:10 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2015-12-01 01:06:10 -07:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2015-12-01 01:06:10 -07:00
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
2017-11-04 02:09:33 +13:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-11-04 02:09:33 +13:00
|
|
|
|
2015-11-27 21:24:11 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-03-05 15:54:08 -05:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
2016-01-27 19:22:58 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
2016-01-27 19:22:58 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
2017-09-17 17:46:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-06 14:32:20 -05:00
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
2019-03-02 10:38:27 -05:00
|
|
|
|
|
|
|
|
|
2017-03-13 11:54:56 -04:00
|
|
|
|
2016-01-31 18:32:07 -07:00
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
2019-03-13 23:15:34 -04:00
|
|
|
|
|
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
2018-02-04 22:06:03 -05:00
|
|
|
|
|
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-21 11:14:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-28 02:22:12 -04:00
|
|
|
|
|
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-18 21:28:06 -04:00
|
|
|
|
|
|
|
|
|
2017-02-03 12:34:20 -05:00
|
|
|
|
|
|
|
|
|
2017-03-13 11:54:56 -04:00
|
|
|
|
|
|
|
|
|
2017-04-19 15:38:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-21 01:56:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
2018-12-26 15:25:54 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
2016-02-11 01:33:27 -07:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2017-09-16 17:00:59 +12:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2017-09-16 17:00:59 +12:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
2017-09-16 17:00:59 +12:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-27 21:24:11 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-08-20 04:25:42 -04:00
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
2017-11-24 14:56:05 -05:00
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
|
|
|
|
|
2017-04-30 18:56:24 -04:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
|
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2017-11-24 14:56:05 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-08-20 04:25:42 -04:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
|
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
2019-02-26 15:51:32 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-13 23:15:34 -04:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
2019-03-02 10:38:27 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2019-02-19 12:07:56 -05:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2019-05-27 20:59:19 -04:00
|
|
|
|
2019-04-14 11:00:37 -04:00
|
|
|
|
2018-06-07 19:10:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-11-24 14:56:05 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-05-11 21:06:31 +02:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2019-05-22 22:14:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-02-11 01:33:27 -07:00
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
|
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-05 00:19:06 -04:00
|
|
|
|
2017-03-31 05:48:15 -04:00
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-04 22:15:53 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-02 10:38:27 -05:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2019-02-19 12:07:56 -05:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
2019-05-27 20:59:19 -04:00
|
|
|
|
2018-12-26 15:25:54 -05:00
|
|
|
|
2018-12-23 22:44:02 -05:00
|
|
|
|
2018-09-11 22:46:22 -04:00
|
|
|
|
2017-04-26 19:17:05 -04:00
|
|
|
|
2017-04-21 01:56:12 -04:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2019-04-14 11:00:37 -04:00
|
|
|
|
2017-02-03 12:34:20 -05:00
|
|
|
|
2017-03-13 13:11:55 -04:00
|
|
|
|
|
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-03-06 13:22:36 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2019-03-13 19:33:19 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
2017-09-18 21:06:53 -04:00
|
|
|
|
2017-09-30 16:59:31 -04:00
|
|
|
|
2017-10-25 23:10:41 -04:00
|
|
|
|
|
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
2019-05-08 20:49:07 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2018-11-02 00:07:43 -04:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2016-09-15 14:05:15 -04:00
|
|
|
|
2016-01-31 18:32:07 -07:00
|
|
|
|
|
|
|
|
|
2016-09-15 14:05:15 -04:00
|
|
|
|
2017-06-14 00:04:34 -04:00
|
|
|
|
|
|
|
|
|
2016-02-27 22:06:46 -07:00
|
|
|
|
2018-02-04 22:06:03 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-15 14:05:15 -04:00
|
|
|
|
2016-09-18 21:28:06 -04:00
|
|
|
|
|
|
|
|
|
2017-03-13 11:54:56 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-31 18:32:07 -07:00
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-12 01:01:06 -03:00
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-12 01:01:06 -03:00
|
|
|
|
2016-02-15 20:56:52 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-11 01:33:27 -07:00
|
|
|
|
2017-04-19 15:38:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 16:35:10 -04:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:18:43 -04:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2017-04-05 07:46:50 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:18:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2017-04-25 12:29:25 -04:00
|
|
|
|
2017-04-27 16:15:41 -04:00
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
|
|
|
|
|
2019-04-10 19:05:05 -05:00
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2019-04-10 19:05:05 -05:00
|
|
|
|
|
|
|
|
|
2019-03-31 16:48:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
|
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
|
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-31 19:04:01 +13:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2019-04-21 17:24:58 -04:00
|
|
|
|
2017-04-25 12:29:25 -04:00
|
|
|
|
breaking changes to zig build API and improved caching
* in Zig build scripts, getOutputPath() is no longer a valid function
to call, unless setOutputDir() was used, or within a custom make()
function. Instead there is more convenient API to use which takes
advantage of the caching system. Search this commit diff for
`exe.run()` for an example.
* Zig build by default enables caching. All build artifacts will go
into zig-cache. If you want to access build artifacts in a convenient
location, it is recommended to add an `install` step. Otherwise
you can use the `run()` API mentioned above to execute programs
directly from their location in the cache. Closes #330.
`addSystemCommand` is available for programs not built with Zig
build.
* Please note that Zig does no cache evicting yet. You may have to
manually delete zig-cache directories periodically to keep disk
usage down. It's planned for this to be a simple Least Recently
Used eviction system eventually.
* `--output`, `--output-lib`, and `--output-h` are removed. Instead,
use `--output-dir` which defaults to the current working directory.
Or take advantage of `--cache on`, which will print the main output
path to stdout, and the other artifacts will be in the same directory
with predictable file names. `--disable-gen-h` is available when
one wants to prevent .h file generation.
* `@cImport` is always independently cached now. Closes #2015.
It always writes the generated Zig code to disk which makes debug
info and compile errors better. No more "TODO: remember C source
location to display here"
* Fix .d file parsing. (Fixes the MacOS CI failure)
* Zig no longer creates "temporary files" other than inside a
zig-cache directory.
This breaks the CLI API that Godbolt uses. The suggested new invocation
can be found in this commit diff, in the changes to `test/cli.zig`.
2019-03-08 22:53:35 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2018-06-29 23:28:42 +02:00
|
|
|
|
|
|
|
|
|
2017-08-30 14:55:26 -04:00
|
|
|
|
|
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
2019-03-13 12:34:54 -04:00
|
|
|
|
2018-09-10 13:46:23 -04:00
|
|
|
|
2018-09-11 20:54:39 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-11 00:32:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
2019-05-22 22:14:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-23 09:35:56 -05:00
|
|
|
|
2017-08-31 11:41:58 -04:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2017-08-30 14:55:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-07 19:58:02 -07:00
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2017-09-17 14:43:51 -04:00
|
|
|
|
|
|
|
|
|
2016-05-07 19:58:02 -07:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2017-11-07 03:22:27 -05:00
|
|
|
|
2016-02-03 18:02:01 -07:00
|
|
|
|
2016-05-07 19:58:02 -07:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-20 04:25:42 -04:00
|
|
|
|
stage1 is now a hybrid of C++ and Zig
This modifies the build process of Zig to put all of the source files
into libcompiler.a, except main.cpp and userland.cpp.
Next, the build process links main.cpp, userland.cpp, and libcompiler.a
into zig1. userland.cpp is a shim for functions that will later be
replaced with self-hosted implementations.
Next, the build process uses zig1 to build src-self-hosted/stage1.zig
into libuserland.a, which does not depend on any of the things that
are shimmed in userland.cpp, such as translate-c.
Finally, the build process re-links main.cpp and libcompiler.a, except
with libuserland.a instead of userland.cpp. Now the shims are replaced
with .zig code. This provides all of the Zig standard library to the
stage1 C++ compiler, and enables us to move certain things to userland,
such as translate-c.
As a proof of concept I have made the `zig zen` command use text defined
in userland. I added `zig translate-c-2` which is a work-in-progress
reimplementation of translate-c in userland, which currently calls
`std.debug.panic("unimplemented")` and you can see the stack trace makes
it all the way back into the C++ main() function (Thanks LemonBoy for
improving that!).
This could potentially let us move other things into userland, such as
hashing algorithms, the entire cache system, .d file parsing, pretty
much anything that libuserland.a itself doesn't need to depend on.
This can also let us have `zig fmt` in stage1 without the overhead
of child process execution, and without the initial compilation delay
before it gets cached.
See #1964
2019-04-16 16:47:47 -04:00
|
|
|
|
2016-02-10 15:41:50 -07:00
|
|
|
|
|
|
|
|
|
2018-09-25 20:13:02 -04:00
|
|
|
|
2019-02-25 11:37:54 -05:00
|
|
|
|
2016-01-31 01:20:47 -07:00
|
|
|
|
2015-11-05 00:05:25 -07:00
|
|
|
|