| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
At least the non-native first phase which takes longer. But maybe a shorter
baseline is the right thing to check. I need to resize some buffers to
get Mu natively translating again.
|
|
|
|
| |
We're now passing CI again.
|
|
|
|
|
|
|
|
| |
I just needed to adjust row-sizes when accessing the Registers table.
This commit dedicated to a fun hour on https://hn.town.siempre.io. Thanks
Cyrus!
(via https://news.ycombinator.com/item?id=22818300)
|
| |
|
|
|
|
| |
For this one commit we need to bootstrap ourselves with subx_translate_debug.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here are the obvious dependencies of different apps:
allocate: mu
slice-to-string: mu survey
new-stream: mu assort dquotes tests
get-or-insert-slice: mu survey assort
get-or-insert: mu survey
So we'll get these working in the following order:
tests
dquotes
assort
survey
It doesn't look like sigils uses any functions with modified signatures,
but it doesn't work at the moment. Let's get the core self-hosted passes
working first before we look at syntax sugar.
examples -> self-hosted passes -> syntax sugar -> mu
|
|
|
|
| |
$ ./translate_subx init.linux 0*.subx && ./a.elf test
|
|
|
|
| |
Some minor tweaks while preparing presentation to Mek's Junto group.
|
|
|
|
| |
Bugfix in CI setup.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Layers 0-89 are used in self-hosting SubX.
Layers 90-99 are not needed for self-hosting SubX, and therefore could
use transitional levels of syntax sugar.
Layers 100 and up use all SubX syntax sugar.
|
|
|
|
| |
Give the bootstrap C++ program a less salient name.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename a few scripts to be more consistent.
I'm also starting to feel the urge to bud off `subx run` into its own program,
say tools/emulate_x86. It doesn't really rely on the SubX notation at all.
And then I could rename `subx translate` to `translate_subx_bootstrap`.
Only problem: the commands in the Readme get verbose. But the Readme is
gonna need surgery soon anyway to put translate_mu front and center.
|
| |
|
| |
|
|
|
|
| |
Add mu.subx to CI.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This undoes 5672 in favor of a new plan:
Layers 000 - 099 are for running without syntax sugar. We use them for
building syntax-sugar passes.
Layers 100 and up are for running with all syntax sugar.
The layers are arranged in approximate order so more phases rely on earlier
layers than later ones.
I plan to not use intermediate syntax sugar (just sigils without calls,
or sigils and calls without braces) anywhere except in the specific passes
implementing them.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The core library is a mess right now, because it can't use syntax sugar.
I need some way to tier the library so that later layers can use syntax
sugar, but without adding cognitive load.
A shell pipeline is pretty, but maybe I need to drop it. Just add functions
to layers. Get all of the translator out of the apps/ sub-directory.
|
|
|
|
|
|
|
|
|
| |
https://github.com/ozkl/soso
+ Much smaller than Linux; builds instantly
+ Supports graphics
- No network support
- Doesn't work on a cloud server (yet?)
|
| |
|
|
|
|
| |
Now added to CI.
|
|
|
|
| |
There's going to be multiple forms of syntax sugar going forward.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Drop a bash-ism.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Stop supporting CFLAGS in CI scripts; they're now meaty enough that I
never run them locally in debug mode.
|
| | |
|
|/ |
|
|
|