about summary refs log tree commit diff stats
path: root/build_and_test_until
Commit message (Collapse)AuthorAgeFilesLines
* 2964Kartik K. Agaram2016-05-151-2/+1
|
* 2946Kartik K. Agaram2016-05-081-22/+2
| | | | | | | | | | | | | Reorganize build system to minimize duplication while handling 3 scenarios: 1. Locally running tests with `mu test` 2. Locally running tests until some layer with `build_and_test_until` 3. Running on Linux with `test_layers` 4. Running on Travis CI with multiple sharded calls to `test_layers` One thing we drop at this point is support for OSX in test_layers. We don't need it now that we have Travis CI working.
* 2942 - switch scripts to bashKartik K. Agaram2016-05-081-2/+2
| | | | | I'm already using grep and perl, bash is no worse, and it's *much* nicer to work in than plain Bourne sh.
* 2934 - all layers running againKartik K. Agaram2016-05-071-2/+2
| | | | | | Since I switched to a Mac laptop (commit 2725) I've been lax in running test_all_layers because I have to ssh into a server and whatnot. I should just get CI setup somewhere..
* 2861 - 'maybe-convert' no longer returns addressKartik K. Agaram2016-04-231-1/+1
|
* 2860 - rename 'index-address' to 'put-index'Kartik K. Agaram2016-04-231-1/+1
|
* 2828Kartik K. Agaram2016-04-101-3/+13
|
* 2778 - fix all layersKartik K. Agaram2016-03-141-0/+2
|
* 2770 - drop a warning from clang 3.4Kartik K. Agaram2016-03-131-1/+1
| | | | | I'm now running valgrind on my Linux server rather than my Mac laptop. Little less convenient; let's see how it goes.
* 2319Kartik K. Agaram2015-10-291-2/+3
|
* 2288Kartik K. Agaram2015-10-271-3/+3
| | | | | | | Make it easy to skip distracting valgrind errors when debugging more obvious errors in early layers. Just throw a 'test' at the end of build_and_test_until commands to not run valgrind (and make it a regular test run).
* 2197Kartik K. Agaram2015-09-141-1/+1
|
* 2002Kartik K. Agaram2015-08-141-3/+1
| | | | | | | | | No, 2001 is no good. Phony targets can't early-exit if everything's built. New approach: $ CFLAGS=-g make && ./mu test etc.
* 1948Kartik K. Agaram2015-08-061-2/+2
|
* 1921 - show trace by clicking on codeKartik K. Agaram2015-08-021-2/+2
| | | | | | | Region to click on to edit is now reduced to just the menu bar for the sandbox (excluding the 'x' for deleting the sandbox). The symmetry there might be useful, but we'll see if the relative click area is in line with how commonly the actions are performed.
* 1623Kartik K. Agaram2015-06-221-2/+3
|
* 1616 - merging keyboard and events into 'console'Kartik K. Agaram2015-06-211-2/+2
| | | | | Only core layers currently passing. Console apps are probably still broken.
* 1300Kartik K. Agaram2015-05-071-1/+2
|
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-1/+1
| | | | | | | | | | | | | | | | | | | All primitives now always write to all their products. If a product is not used that's fine, but if an instruction seems to expect too many products mu will complain. In the process, many primitives can operate on more than two ingredients where it seems intuitive. You can add or divide more than two numbers together, copy or negate multiple corresponding locations, etc. There's one remaining bit of ugliness. Some instructions like get/get-address, index/index-address, wait-for-location, these can unnecessarily load values from memory when they don't need to. Useful vim commands: %s/ingredients\[\([^\]]*\)\]/ingredients.at(\1)/gc %s/products\[\([^\]]*\)\]/products.at(\1)/gc .,$s/\[\(.\)]/.at(\1)/gc
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+11
I've tried to update the Readme, but there are at least a couple of issues.