Displaying 6 results from an estimated 6 matches for "managingmemory".
2007 Jul 14
0
[LLVMdev] JIT Leaks?
On 2007-07-14, at 13:56, Anton Korobeynikov wrote:
>> You can find out what exactly leaks with the help of valgrind.
>
> It seems, that Paolo is on Mac OS X. No valgrind there :(
All is not lost…
http://developer.apple.com/documentation/Performance/Conceptual/
ManagingMemory/Articles/FindingLeaks.html
— Gordon
2007 Jul 15
2
[LLVMdev] JIT Leaks?
...at 13:56, Anton Korobeynikov wrote:
>
>>> You can find out what exactly leaks with the help of valgrind.
>>
>> It seems, that Paolo is on Mac OS X. No valgrind there :(
>
> All is not lost…
>
> http://developer.apple.com/documentation/Performance/Conceptual/
> ManagingMemory/Articles/FindingLeaks.html
>
> — Gordon
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2007 Jul 14
4
[LLVMdev] JIT Leaks?
Holger.
> You can find out what exactly leaks with the help of valgrind.
It seems, that Paolo is on Mac OS X. No valgrind there :(
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2007 Jul 15
0
[LLVMdev] JIT Leaks?
...>>
>>>> You can find out what exactly leaks with the help of valgrind.
>>>
>>> It seems, that Paolo is on Mac OS X. No valgrind there :(
>>
>> All is not lost…
>>
>> http://developer.apple.com/documentation/Performance/Conceptual/
>> ManagingMemory/Articles/FindingLeaks.html
>>
>> — Gordon
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>...
2020 Jul 13
2
FileCheck --allow-empty
Hi all,
By default, FileCheck will emit an error if you try to get it to check an
empty file. This doesn't seem like a bad idea to me, since it might protect
against certain unintended usages. However, in every use-case I know of,
it's also combined with checks that essentially say "don't just allow the
output to be empty, fail if it isn't". In some cases, those checks
2016 Nov 17
2
UB in MemoryBufferMMapFile
Chris Lattner <clattner at apple.com> writes:
> On Nov 16, 2016, at 9:46 PM, Justin Bogner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> In MemoryBuffer::init, we have an assert that reads the memory at
>> `BufEnd`, which is one past the end of some memory region:
>>
>> from lib/Support/MemoryBuffer.cpp:45:
>>> void