| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 3898 | Kartik K. Agaram | 2017-05-31 | 1 | -34/+14 |
| | | | | | | | | | | | | There seems to be some chance of speed-up when I inline these functions. However, it's not a clear enough signal to justify improving the `build` script to handle the `inline` keyword. Current timing experiments: Before After ubuntu 1GB 9:22,8:48,8:51,9:16,9:17,8:36,9:05 8:55,8:41,8:15,8:27,8:29,8:54,9:29 OS X 8GB 4:05,4:00,4:18,4:09,3:40,3:51,3:56 3:58,3:52,4:01,4:13,4:16,4:31,4:13 | ||||
| * | 3889 - profile refcount updates by recipe | Kartik K. Agaram | 2017-05-29 | 1 | -3/+4 |
| | | | | | | We're currently spending 50% of our time in `mu edit` performing refcount updates. | ||||
| * | 3888 - beginnings of a profiler | Kartik K. Agaram | 2017-05-28 | 1 | -0/+5 |
| | | | | | Time to make my ad hoc commented out code fragments a first-class feature. | ||||
| * | 3887 - clean up early exits in interpreter loop | Kartik K. Agaram | 2017-05-28 | 1 | -14/+13 |
| | | | | | | | | | | | It's always confusing when `break` refers to a `switch` but `continue` refers to the loop around the `switch`. But we've done ugly things like this and `goto` for expedience. However, we're starting to run into cases where we now need to insert code at every `continue` or `continue`-mimicking `goto` inside the core interpreter loop. Better to make the loop single-entry-single-exit. Common things to run after every instruction will now happen inside the `finish_instruction` function rather than at the `finish_instruction` label. | ||||
| * | 3877 | Kartik K. Agaram | 2017-05-26 | 1 | -1/+1 |
| | | |||||
| * | 3809 | Kartik K. Agaram | 2017-04-04 | 1 | -2/+2 |
| | | |||||
| * | 3803 | Kartik K. Agaram | 2017-03-20 | 1 | -1/+1 |
| | | |||||
| * | 3380 | Kartik K. Agaram | 2016-09-17 | 1 | -8/+8 |
| | | | | | | One more place we were missing expanding type abbreviations: inside container definitions. | ||||
| * | 3358 | Kartik K. Agaram | 2016-09-15 | 1 | -0/+5 |
| | | |||||
| * | 3279 | Kartik K. Agaram | 2016-08-29 | 1 | -12/+12 |
| | | | | | | Stop inlining functions because that will complicate separate compilation. It also simplifies the code without impacting performance. | ||||
| * | 3120 | Kartik K. Agaram | 2016-07-21 | 1 | -1/+1 |
| | | | | | | | | | Always show instruction before any transforms in error messages. This is likely going to make some errors unclear because they *need* to show the original instruction. But if we don't have tests for those situations did they ever really work? | ||||
| * | 3105 | Stephen Malina | 2016-07-06 | 1 | -1/+1 |
| | | | | | Add number-of-instructions recipe to Mu | ||||
| * | 2862 | Kartik K. Agaram | 2016-04-24 | 1 | -0/+168 |
| Layers 0-29 are now a complete rudimentary platform except for pointers and indirection. | |||||