about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1196Kartik K. Agaram2015-04-242-1/+1
|
* 1195Kartik K. Agaram2015-04-242-0/+41
|
* 1194Kartik K. Agaram2015-04-24103-1/+107
|
* 1193Kartik K. Agaram2015-04-2416-80/+94
|
* 1192Kartik K. Agaram2015-04-242-19/+18
|
* 1191Kartik K. Agaram2015-04-241-1/+2
|
* 1190Kartik K. Agaram2015-04-241-7/+4
|
* 1189 - add extensions to all layersKartik K. Agaram2015-04-2436-3/+0
| | | | | | I'm sick of fighting vim's filetype detection. No modeline and files highlight in random colors. I add a modeline and it stops highlighting tangle comments. Even though it read my #$%# vimrc! Fuck this shite.
* 1188Kartik K. Agaram2015-04-242-6/+6
|
* 1187Kartik K. Agaram2015-04-242-2/+62
|
* 1186Kartik K. Agaram2015-04-242-3/+0
|
* 1185 - inline C++ in scenariosKartik K. Agaram2015-04-245-23/+9
|
* 1184 - finally, concurrencyKartik K. Agaram2015-04-24119-65/+229
|
* 1183Kartik K. Agaram2015-04-244-0/+7
|
* 1182Kartik K. Agaram2015-04-242-9/+0
|
* 1181Kartik K. Agaram2015-04-242-6/+4
| | | | Purge unordered_* from subdirectories as well.
* 1180 - finally dump that 'pc' referenceKartik K. Agaram2015-04-242-4/+2
| | | | | | In the process we uncovered yet another out-of-bounds access, in the implementation of 'reply'. Another sign from the gods that large-scope pointers/references are a bad idea.
* 1179Kartik K. Agaram2015-04-242-9/+6
|
* 1178Kartik K. Agaram2015-04-241-3/+2
|
* 1177Kartik K. Agaram2015-04-244-7/+7
|
* 1176Kartik K. Agaram2015-04-243-9/+9
|
* 1175Kartik K. Agaram2015-04-242-8/+0
|
* 1174Kartik K. Agaram2015-04-241-1/+1
|
* 1173Kartik K. Agaram2015-04-242-4/+4
|
* 1172Kartik K. Agaram2015-04-242-11/+11
|
* 1171Kartik K. Agaram2015-04-2416-155/+162
| | | | | Chip away at eliminating that 'pc' reference by first throwing out the most common expression that uses it: instructions[pc].
* 1170Kartik K. Agaram2015-04-243-8/+10
|
* 1169 - use the global variable god gave youKartik K. Agaram2015-04-245-53/+56
|
* 1168Kartik K. Agaram2015-04-2414-76/+76
|
* 1167Kartik K. Agaram2015-04-241-1/+1
|
* 1166Kartik K. Agaram2015-04-2414-46/+41
| | | | | | | Why did I think STL's map wasn't efficient? It has logarithmic complexity (maintains a tree internally) and is faster than hashing for small containers. It's the more portable solution and should be what I turn to by default.
* 1165Kartik K. Agaram2015-04-241-2/+2
|
* 1164Kartik K. Agaram2015-04-241-0/+3
|
* 1163Kartik K. Agaram2015-04-244-11/+11
|
* 1162Kartik K. Agaram2015-04-2423-99/+99
|
* 1161Kartik K. Agaram2015-04-241-1/+1
|
* 1160Kartik K. Agaram2015-04-241-1/+1
|
* 1159Kartik K. Agaram2015-04-242-2/+2
|
* 1158Kartik K. Agaram2015-04-241-14/+15
|
* 1157Kartik K. Agaram2015-04-241-3/+3
|
* 1156Kartik K. Agaram2015-04-241-1/+1
|
* 1155 - three phases of mu: load, transform, runKartik K. Agaram2015-04-247-22/+18
| | | | | | Each phase implicitly calls previous phases. Most C++ scenarios implicitly call one, two or three of the phases. More clear now that 'load' does more than just add recipes.
* 1154Kartik K. Agaram2015-04-241-1/+1
|
* 1153 - start of scheduler implementationKartik K. Agaram2015-04-232-2/+23
| | | | | This first step is just stopping run() after a fixed number of instructions. But the scheduler layer isn't done yet.
* 1152Kartik K. Agaram2015-04-231-7/+0
|
* 1151Kartik K. Agaram2015-04-233-10/+32
|
* 1150Kartik K. Agaram2015-04-231-1/+0
|
* 1149Kartik K. Agaram2015-04-231-0/+7
|
* 1148 - valgrind ALL the things!Kartik K. Agaram2015-04-222-2/+5
|
* 1147 - one final memory leak; now valgrind-cleanKartik K. Agaram2015-04-221-1/+0
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-15 16:58:09 +0000