Displaying 3 results from an estimated 3 matches for "16384g".
Did you mean:
16384
2011 Jun 17
0
[LLVMdev] LLVM-based address sanity checker
On 17 June 2011 08:55, Kostya Serebryany <kcc at google.com> wrote:
> I am rather reluctant to add 'generic' code that handles unknown/untested
> platforms because the memory mapping is very platform specific anyway.
Indeed, but the point of that is more for helping writing
platform-specific versions than actually using it as a general-purpose
routine. Kinda documentation of
2011 Jun 17
2
[LLVMdev] LLVM-based address sanity checker
On Fri, Jun 17, 2011 at 11:48 AM, Renato Golin <rengolin at systemcall.org>wrote:
> On 16 June 2011 20:57, Kostya Serebryany <kcc at google.com> wrote:
> >> I see, maybe you could leave your C implementation as a fall back.
> >
> > Not easy, because it will require a fallback code in the run time
> library.
> > But yes, possible.
>
> I was
2011 Jun 17
3
[LLVMdev] LLVM-based address sanity checker
...SEGV handler mmaps the required region.
> If I'm not mistaken, the Native Client
> guys have done a memory place-holder, with enough space pre- and
> post-code, is it similar of what you're doing?
Not very similar. 64-bit NaCl mmaps 88G of address space. On 64-bit ASAN I
need 16384G of RAM, which is a bit too much to mmap.
> Or are you using a big
> BSS region?
>
> Depending on how you did it, it might just work on other platforms...
>
> cheers,
> --renato
>
--kcc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <htt...