Displaying 20 results from an estimated 11654 matches for "dieing".
2013 Oct 16
2
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
> In beginModule, we construct the CUs, but not all the DIEs that belong to
>>> the CU.
>>> In endFunction, we started to construct the scope DIEs. So in some
>>> sense, we are adding things to prior CUs.
>>>
>>> Looking at void CompileUnit::addDIEEntry(DIE *Die, uint16_t Attribute,
>>> DIE *Entry), we can possibly have 3 CUs, this CU,
2013 Oct 16
3
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Wed, Oct 16, 2013 at 10:54 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>>
>> In beginModule, we construct the CUs, but not all the DIEs that belong
>>>>> to the CU.
>>>>> In endFunction, we started to construct the scope DIEs. So in
2013 Oct 16
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Wed, Oct 16, 2013 at 11:10 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Wed, Oct 16, 2013 at 10:54 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>> In beginModule, we construct the CUs, but not all
2013 Oct 16
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
> In beginModule, we construct the CUs, but not all the DIEs that belong
>>>> to the CU.
>>>> In endFunction, we started to construct the scope DIEs. So in some
>>>> sense, we are adding things to prior CUs.
>>>>
>>>> Looking at void
2013 Oct 16
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 5:22 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 4:59 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 2:24 PM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2013 Oct 16
2
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 4:59 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 2:24 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 1:56 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2013 Oct 16
3
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Wed, Oct 16, 2013 at 11:54 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Wed, Oct 16, 2013 at 11:10 AM, David Blaikie <dblaikie at gmail.com>wrote:
>
>>
>>
>>
>> On Wed, Oct 16, 2013 at 10:54 AM, Manman Ren <manman.ren at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2015 May 20
5
[LLVMdev] RFC: Reduce the memory footprint of DIEs (and DIEValues)
Pete Cooper and I have been looking at memory profiles of running llc on
verify-uselistorder.lto.opt.bc (ld -save-temps dump just before CodeGen
of building verify-uselistorder with -flto -g). I've attached
leak-backend.patch, which we're using to make Intrustruments more
accurate (instead of effectively leaking things onto BumpPtrAllocators,
really leak them with malloc()). (I've
2013 Oct 17
1
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Wed, Oct 16, 2013 at 10:32 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Wed, Oct 16, 2013 at 9:10 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Wed, Oct 16, 2013 at 1:58 PM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Wed, Oct 16, 2013 at
2013 Oct 15
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 2:24 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 1:56 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 1:37 PM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2013 Oct 15
4
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 1:56 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 1:37 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 1:22 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2013 Oct 16
2
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
There are a few places where we break the assumption:
1> formal_parameter constructed in DwarfDebug when adding attribute type
we call SPCU->addType(Arg, ATy), where Arg does not belong to SPCU.
2> inlined_subroutine constructed in DwarfDebug when adding attribute
abstract_origin
The inlined_subroutine does not belong to the CU we call addDIEEntry
on.
We create the children
2012 Apr 08
1
DLLs for Orcs Must Die
Hi,
I could install Orcs Must Die, but when I try to run it, I get the following errors:
Code:
err:module:import_dll Library fmod_event.dll (which is needed by L"C:\\Programme (x86)\\Robot Entertainment\\Orcs Must Die!\\Build\\release\\OrcsMustDie.exe") not found
err:module:import_dll Library lua90.dll (which is needed by L"C:\\Programme (x86)\\Robot Entertainment\\Orcs Must
2013 Mar 09
1
[LLVMdev] Question about abstract subprograms in debug info
Hi,
I am working on an issue where a subprogram created here is having abstract_origin pointing to nowhere.
DIE *DwarfDebug::updateSubprogramScopeDIE(CompileUnit *SPCU,
const MDNode *SPNode) {
DIE *SPDie = SPCU->getDIE(SPNode);
assert(SPDie && "Unable to find subprogram DIE!");
DISubprogram SP(SPNode);
// If we're
2011 Mar 30
0
[LLVMdev] More DWARF problems
On Mar 29, 2011, at 7:29 PM, Talin wrote:
> I've been trying to track down the problem with the DWARF info that is being emitted by my front end, which has been broken for about a month now. Here's what happens when I attempt to use gdb to debug one of my programs on OS X:
>
> gdb stack crawl at point of internal error:
> [ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin
2010 Aug 22
2
[LLVMdev] "Cannot fine DIE"
I recently started getting this error when I try to debug my LLVM-compiled
program in GDB:
Dwarf Error: Cannot find DIE at 0x16769 referenced from DIE at 0x1713c
[in module
/home/talin/Projects/tart/build-eclipse/test/stdlib/ReflectionTest]
I'm not sure if it's something I did or not. Is there any way to track down
the cause of this error? The hex addresses in the error message are
2013 Oct 15
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 1:37 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 1:22 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 11:34 AM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2013 Oct 15
2
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 1:22 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Tue, Oct 15, 2013 at 11:34 AM, David Blaikie <dblaikie at gmail.com>wrote:
>
>>
>>
>>
>> On Tue, Oct 15, 2013 at 10:51 AM, Manman Ren <manman.ren at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 15, 2013 at
2011 Mar 30
5
[LLVMdev] More DWARF problems
I've been trying to track down the problem with the DWARF info that is being
emitted by my front end, which has been broken for about a month now. Here's
what happens when I attempt to use gdb to debug one of my programs on OS X:
gdb stack crawl at point of internal error:
[ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300]
[ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin
2011 Apr 03
2
[LLVMdev] More DWARF problems
On Wed, Mar 30, 2011 at 11:17 AM, Devang Patel <dpatel at apple.com> wrote:
>
> On Mar 29, 2011, at 7:29 PM, Talin wrote:
>
> I've been trying to track down the problem with the DWARF info that is
> being emitted by my front end, which has been broken for about a month now.
> Here's what happens when I attempt to use gdb to debug one of my programs on
> OS X: