Displaying 2 results from an estimated 2 matches for "dismantleengin".
2015 Oct 01
2
Pool allocator + safecode
...o check why the suggestion was not to use it. Has it been
superseded in some way by something else? Or is it just broken at the
moment? I'll assume the latter for now and see if I can fix it...
Cheers
[1] http://lists.llvm.org/pipermail/llvm-dev/2015-July/088739.html
--
Ed Robbins
ed at dismantleengineering.co.uk
2015 Oct 09
2
llvm-dev Digest, Vol 136, Issue 22
(Note to self: learn to scan the full digest for later messages in a thread before replying to an earlier message.)
Ed,
Your reply to John answered some of my questions, but not all, and raised a new one:
> Maybe I should have been a bit clearer; we're really interested in full
> memory and type safety. We want to harden the system against memory
> corruption vulnerabilities.