about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 4455 - support displacement in ModR/MKartik Agaram2018-07-302-11/+48
| | | | Really ugly solution.
* 4454Kartik Agaram2018-07-301-2/+2
|
* 4453Kartik Agaram2018-07-301-2/+2
| | | | Got a couple of instructions mixed up.
* 4452Kartik Agaram2018-07-301-2/+5
| | | | Keep a few macros more tightly scoped to just the transform they're used in.
* 4451Kartik Agaram2018-07-301-3/+2
|
* 4450Kartik Agaram2018-07-302-0/+31
|
* 4449Kartik Agaram2018-07-284-19/+14
|
* 4448Kartik Agaram2018-07-271-4/+56
|
* 4447Kartik Agaram2018-07-27137-16727/+22050
|
* 4446Kartik Agaram2018-07-277-49/+55
|
* 4445 - support labelsKartik Agaram2018-07-274-31/+102
|
* 4444Kartik Agaram2018-07-276-29/+40
| | | | More tracing reorg.
* 4443Kartik Agaram2018-07-271-5/+9
|
* 4442Kartik Agaram2018-07-2711-93/+93
| | | | Clean up trace levels everywhere in SubX.
* 4441Kartik Agaram2018-07-271-4/+4
|
* 4440Kartik Agaram2018-07-271-0/+2
|
* 4439Kartik Agaram2018-07-271-8/+5
|
* 4438Kartik Agaram2018-07-271-1/+1
|
* 4437 - support for labels is half-doneKartik Agaram2018-07-272-0/+97
|
* 4436Kartik Agaram2018-07-271-2/+8
|
* 4435 - make instruction packing less strictKartik Agaram2018-07-272-1/+26
| | | | | | Now it will pass labels straight through. But we may get more confusing error messages in later passes in some situations.
* 4434Kartik Agaram2018-07-2711-197/+209
| | | | | | | | Key core data structures by hex bytes in text rather than opcode numbers. Saves us round trips of having to parse and reparse strings, and also allows us to more easily ignore unexpected non-hex words in each transform. We'll use this ability next when we start inserting labels.
* 4433Kartik Agaram2018-07-271-3/+3
|
* 4432Kartik Agaram2018-07-263-9/+9
| | | | | Good idea from @tekknolagi: make more explicit that the first segment is code.
* 4431 - operate exclusively in hexKartik Agaram2018-07-267-15/+13
| | | | | | | | | Was confusing having numbers without an explicit base sometimes be hex and sometimes not, based on their metadata. By convention I don't bother with the '0x' for instructions, or for single-digit numbers that are equal to their decimal representation. But I could and it would still work.
* 4430Kartik Agaram2018-07-263-26/+26
|
* 4429 - syntax checking for multi-byte opcodesKartik Agaram2018-07-261-2/+49
| | | | We don't have any supported 3-byte opcodes at the moment.
* 4428Kartik Agaram2018-07-261-0/+2
| | | | Fix CI :(
* 4427 - support for '--trace' argvKartik Agaram2018-07-263-13/+49
| | | | This ports commit 4421 to the subx/ program.
* 4426 - error on unrecognized sub-commandsKartik Agaram2018-07-264-2/+13
|
* 4425Kartik Agaram2018-07-261-1/+4
| | | | Better name for a layer.
* 4424Kartik Agaram2018-07-267-71/+70
| | | | Clean up format of example programs.
* Merge pull request #17 from tekknolagi/masterKartik Agaram2018-07-261-14/+28
|\ | | | | Use semicolons instead of commas for sequencing
| * Use semicolons instead of commas for sequencingMaxwell Bernstein2018-07-261-14/+28
|/
* 4423Kartik Agaram2018-07-261-8/+5
| | | | Silence some messages to the console. Fixes #12.
* 4422Kartik Agaram2018-07-262-8/+5
|
* 4421Kartik Agaram2018-07-265-41/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clean up the rat's nest that all my trace management globals had gradually turned into. a) Get rid of 'Start_tracing'. Horryibly named, I don't know how I missed that until now. b) Never use START_TRACING_UNTIL_END_OF_SCOPE in main(). It's confusing to combine it with atexit(delete Trace_stream), because the atexit() never has to run. Instead we'll just manually initialize Trace_stream and let atexit() clean up. c) If we run tests we only want a trace for the test run itself. So delete the Trace_stream that was initialized at the top of main -- once it's clear we had no load-time errors. d) Clean up horribly "Load Recipes" waypoints, combine them with the better name, "Mu Prelude". Putting these together, we have the following manual tests: - CFLAGS=-g mu x.mu Should not create last_run. - CFLAGS=-g mu --trace x.mu Should create last_run. Should write it out exactly once. - CFLAGS=-g mu --trace x.mu # when x.mu has an error Should create last_run. Should write it out exactly once. - CFLAGS=-g mu --trace test copy_literal # C test Should create last_run. Should write it out exactly once. - CFLAGS=-g mu --trace test recipe_with_header # Mu test Should create last_run. Should write it out exactly once. I don't know how to automate these scenarios yet. We need a way to run our build toolchain atop our stack.
* 4420Kartik Agaram2018-07-261-6/+6
|
* 4419Kartik Agaram2018-07-261-2/+2
| | | | Unshadow variable. Thanks Max Bernstein for pointing this out.
* 4418Kartik Agaram2018-07-264-8/+8
| | | | | Use 'dump' consistently to mean 'to screen' (stderr), and 'save' to mean 'to disk'.
* 4417Kartik Agaram2018-07-262-2/+2
| | | | Audit poor uses of 'cout'.
* 4416 - start collecting traces in runsKartik Agaram2018-07-261-0/+1
| | | | | | To see traces on stdout, set the global `Dump_trace` to true. Thanks Max Bernstein for the feedback.
* Merge pull request #15 from tekknolagi/patch-1Kartik Agaram2018-07-251-2/+2
|\ | | | | Update dependency in Readme
| * Update dependency in ReadmeMax Bernstein2018-07-251-2/+2
|/
* 4415Kartik Agaram2018-07-251-3/+7
|
* 4414 - subx: syntax checkingKartik Agaram2018-07-2510-121/+920
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a large patch, and there's a few things wrong with it: a) Helpers are incredibly messy. I want to use has_metadata in layer 24, but can't since it also does error checking. There must be a better basis set of primitives for managing metadata. b) Layer 22 introduces operands for checking, but programs with operands don't actually run until layer 24. So I can't write non-error scenarios in layer 22. That seems ugly. But if I try to introduce layer 24 first there's nothing left to check after it. I *could* play tricks with ordering layers vs transforms. Mu does that a bit, but it becomes hard to mess with, so I'm trying to avoid that. My current plan is for layers within an "abstraction level" to be run in order. Higher layers will necessarily need to come before lower ones. But hopefully this level of hierarchy will help manage the chaos. c) The check for whether an instruction is all hex bytes makes me nervous. I do want to check that an instruction that's just: cd tells the programmer that an operand is missing. The check I currently have is likely not perfectly correct. I *could* put layer 25 in its own commit. But I guess I'm not doing that now. We have a new example program: hello world!
* 4413Kartik Agaram2018-07-258-14/+10
| | | | | Never mind, let's drop unused/vestigial altogether. Use absence of names to signal unused arguments.
* 4412Kartik Agaram2018-07-254-5/+5
| | | | Drop names of unused arguments.
* 4411Kartik Agaram2018-07-253-5/+9
| | | | Port commit 4235 to subx.
* 4410Kartik Agaram2018-07-251-145/+0
| | | | | Temporarily delete support for /imm tags. We'll bring it back momentarily in a totally different way.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-03 21:57:57 +0000