about summary refs log tree commit diff stats
path: root/makefile
Commit message (Collapse)AuthorAgeFilesLines
* 3107 - just always support small VPS serversKartik K. Agaram2016-07-101-0/+2
| | | | | In experiments on my laptop it seems to compile a little faster and run slightly slower. Both might be in the noise.
* 3026 - integer overflow protectionKartik K. Agaram2016-06-021-1/+1
| | | | | | | How did I not know about -ftrapv for so long?! Found while reading Memarian et al, "Into the depths of C: Elaborating the de facto standards". http://www.cl.cam.ac.uk/~pes20/cerberus/pldi16.pdf
* 2946Kartik K. Agaram2016-05-081-3/+0
| | | | | | | | | | | | | 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.
* 2725 - dev machine is now MacKartik K. Agaram2016-03-021-0/+1
|
* 2684Kartik K. Agaram2016-02-221-1/+1
|
* 2665Kartik K. Agaram2016-02-171-1/+1
|
* move enumerate, tangle dependencies to mu.ccThomas van der Berg2016-02-131-2/+2
|
* 2288Kartik K. Agaram2015-10-271-0/+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).
* 2067Kartik K. Agaram2015-08-241-2/+2
|
* 2002Kartik K. Agaram2015-08-141-28/+7
| | | | | | | | | No, 2001 is no good. Phony targets can't early-exit if everything's built. New approach: $ CFLAGS=-g make && ./mu test etc.
* 2001Kartik K. Agaram2015-08-141-27/+31
| | | | | | | | | | | | | | | | | | Let's stop hackily editing compiler flags in makefile. I considered modifying the 'mu' script as well, with cases like this: 1. mu test -- don't optimize 2. mu test edit.mu -- optimize 3. mu test edit.mu just-one-test -- don't optimize 4. mu edit.mu -- interactive; optimize 5. mu -- just help message; don't optimize But that seems brittle for all the added complexity. From now on to build quickly just do: $ make dbg && mu test etc.
* 1998Kartik K. Agaram2015-08-141-2/+11
| | | | | Spent a while trying to understand why editing a slightly larger program was so much slower. Then realized I'd managed to disable optimizations.
* 1990 - extra ingredient for 'trace' depthKartik K. Agaram2015-08-131-1/+1
| | | | Now we can make use of all the depths from 1 to 99.
* 1976 - fix 'make test'Kartik K. Agaram2015-08-111-2/+2
|
* 1878 - switch test_all_layers to optimized binariesKartik K. Agaram2015-07-281-1/+1
| | | | | | | The cost of optimization across all levels is now lower than that of running them unoptimized. test_all_layers unoptimized: 22:36.88 test_all_layers optimized: 19:33.38
* 1842 - get layers building again after 2 weeksKartik K. Agaram2015-07-241-4/+4
| | | | | Also, turns out I haven't been building 999spaces.cc in my default build. Now fixed.
* 1794 - stop redundantly recompiling on .mu changesKartik K. Agaram2015-07-161-2/+6
|
* 1706 - automatically recompile mu when necessaryKartik K. Agaram2015-07-041-9/+9
|
* 1659 - still a little sluggishKartik K. Agaram2015-06-251-1/+1
| | | | | | | | Time to turn on optimizations, since we aren't recompiling mu all the time anymore. But it doesn't help much with the editor. We need to be smarter about not rendering the whole screen.
* 1619Kartik K. Agaram2015-06-221-1/+1
|
* 1573Kartik K. Agaram2015-06-161-1/+1
|
* 1439 - support clang in addition to gccKartik K. Agaram2015-05-231-1/+1
|
* 1424 - the right way to make autogenerated_listsKartik K. Agaram2015-05-221-1/+2
| | | | | Ever since 1403 mu depended on a phony target and so was always considered stale. This commit improves on that fix.
* 1405Kartik K. Agaram2015-05-191-1/+7
|
* 1404 - undefined-behavior checks using clangKartik K. Agaram2015-05-181-2/+5
| | | | | | | | While I'm at it I also explored turning on optimization. With optimization compile+test of the chessboard app takes 10+3s, while without optimization it takes 3+8s. So we're still better off without optimizations in a tight debug loop. (Since we stopped tracing the big chessboard test.)
* 1403Kartik K. Agaram2015-05-181-7/+6
|
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+52
I've tried to update the Readme, but there are at least a couple of issues.