about summary refs log tree commit diff stats
path: root/085scenario_console.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2773 - switch to 'int'Kartik K. Agaram2016-03-131-21/+21
| | | | This should eradicate the issue of 2771.
* 2771 - fix for clang on 32-bit machinesKartik K. Agaram2016-03-131-1/+1
| | | | | | | | | | | Turns out that LLVM/Clang still doesn't support multiplying 64-bit numbers on a 32-bit platform. https://llvm.org/bugs/show_bug.cgi?id=14469 This is just a quick fix, because it turns out I don't have any integer multiplication anywhere else. In the long run I think I'm going to just drop 'long long int' in favor of 'int'. Overflow is less likely than this configuration on somebody's machine.
* 2767 - reclaim refcounts for local variablesKartik K. Agaram2016-03-121-0/+2
| | | | | | This uncovered a second bug (besides 2766) -- I was manually doing the work of 'new-fake-console' inside 'assume-console' but forgetting to increment a refcount.
* 2712Kartik K. Agaram2016-02-261-2/+2
|
* 2677Kartik K. Agaram2016-02-201-2/+2
| | | | Include type names in the type tree. Though we aren't using them yet.
* 2581 - make space for the refcount in address:sharedKartik K. Agaram2016-01-201-5/+13
| | | | | | | | | | | We don't yet actually maintain the refcount. That's next. Hardest part of this was debugging the assume-console scenarios in layer 85. That took some detailed manual diffing of traces (because the output of diff was no good). New tracing added in this commit add 8% to .traces LoC. Commented out trace() calls (used during debugging) make that 45%.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-10/+10
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2430 - make room for more transformsKartik K. Agaram2015-11-131-0/+287