emeryberger

12 ms·

91.
by emeryberger 11y ago
We (PLASMA @ UMass, http://plasma.cs.umass.edu ) have a project with similar aims that is somewhat further along: Ninia ( https://github.com/plasma-umass/Ninia ). Ninia is a Python bytecode interpreter in Type
92.
by emeryberger 11y ago
Glad you said this - it's a pain point, for sure. My PhD student Charlie Curtsinger (who will be joining Grinnell College this Fall) developed Stabilizer using LLVM (see http://emeryberger.com/research/stabilizer&#
93.
by emeryberger 12y ago
It's not that unusual these days. Jason Flinn (Michigan) has published quite a few papers that root out causality in various settings. The use of causality via happens-before relationships has been part of distributed and concurrent sy
94.
by emeryberger 12y ago
Thanks for posting. We have a technical report describing how Coz works in detail. The current implementation profiles Linux x86-64 binaries. Causal Profiling: Finding Optimizations that Count ( https://web.cs.umass.edu/pub
95.
by emeryberger 12y ago
No good reason for why it hasn't changed, except that the underlying single-threaded allocator (Doug Lea's malloc) is really good. The multithreaded version, which is a "per-thread" (not really) wrapper around the Lea al
96.
by emeryberger 12y ago
Sure, it's not officially news, but it's apparently news to Hacker News.
97.
by emeryberger 12y ago
Actually, the codebase continues to be actively updated.
98.
by emeryberger 12y ago
What you are referring to is not DieHard but rather Exterminator. DieHard probabilistically tolerates memory errors, while Exterminator repairs them. Both rely on a carefully designed semantics under which one can provide a reasonable inter
99.
by emeryberger 12y ago
DieHard directly inspired the Windows Fault-Tolerant Heap, and follow-on work (DieHarder) inspired security hardening features in Windows. Follow-on work from DieHard, which probabilistically tolerates memory errors, includes the following: