[0:58:24][@d7samurai][In the visual studio output window you can right click and deselect some of the stuff]
[0:58:56][@cubercaleb][Why does this have to be so complicated??]
[0:59:37][@rc1290][Why did you put the memory barrier in a macro when it's platform-specific code?]
[1:00:07][@robrobby][After the sleep, some threads still pushed several strings, leaving out some of the other threads]
[1:00:56][@plain_flavored][Would Sleep(0) in your spin-lock help anything?]
[1:02:35][@abnercoimbre][IMGUI has been trending. Sorry if you get asked this more than you like to.]
[1:03:07][@goodjerm][When you initially started this project, what were the first 5 things you coded and why?]
[1:03:22][@ifingerbangedurcat][I missed most of tonight, what does the volatile keyword mean?]
[1:03:47][@noxy_key][How do you plan to maintain cache line coherency between processors? Can physical CPUs share a cache line?]
[1:05:03][Blackboard: MESI and Cache Coherency]
[1:14:15][@gasto5][Was volatile added in C99?]
[1:14:37][@abnercoimbre][Wait, so transactional memory wants to simplify concurrent programming by allowing a chunk of load/store instructions to execute in atomically. Have you messed with this?]
[1:15:05][Blackboard: Transactional Memory]
[1:18:58][@abnercoimbre][Transactional memory is often advocated as an easier-to-use replacement for locks that avoids any possibility of a deadlock, so I wanted your thoughts.]
[1:21:04][@plainflavored][Why are we building a generic work distribution when the tiled renderer is designed to cleanly split up the work anyway?]
