Displaying 10 results from an estimated 10 matches for "gfull".
Did you mean:
full
2016 May 06
3
RFC: metadata attachments for global variables
...l useful
>
>>> - When clang compiles debug info for a module it compiles an otherwise empty CU with debug info for all types in the module.
>>
>> - (something we recently discussed on cfe-commits for better supporting dtrace/ctfconvert) because the frontend implemented a -gfull option that added all types to the CU’s list retained types.
>
> Ok, you can have the named metadata to retain specific CU, but that could be the exception and not the rule.
Given the enum example, I’m not entirely convinced that there will be many CUs that are not the exception, but genera...
2016 May 06
2
RFC: metadata attachments for global variables
...urce/xnu/xnu-1456.1.26/config/version.c).
> - When clang compiles debug info for a module it compiles an otherwise empty CU with debug info for all types in the module.
- (something we recently discussed on cfe-commits for better supporting dtrace/ctfconvert) because the frontend implemented a -gfull option that added all types to the CU’s list retained types.
> -- adrian
>
>> --
>> Mehdi
>>
>>
>>> We will also need a story for preserving DIGlobalVariables that are constants and have their GlobalObject optimized away. We can definitely remove all the...
2016 Mar 30
0
[RFC] Lazy-loading of debug info metadata
...;> already been loaded in the main module.
The essential things I want to accomplish with this part:
- Make `type:` operands less special: instead of referencing types
indirectly through MDString, point directly at the type node.
- Stop using `retainedTypes:` by default (only for -gfull, etc.).
- Avoid blowing up memory in -flto=full (which converting MDString
references back to pointers would do naively, through
re-introducing cycles). Note that this needs to be handled
somehow at BitcodeReader time.
After chatting with Eric, I don't think this conflicts at a...
2016 Mar 30
3
[RFC] Lazy-loading of debug info metadata
...the main module.
>
> The essential things I want to accomplish with this part:
>
> - Make `type:` operands less special: instead of referencing types
> indirectly through MDString, point directly at the type node.
>
> - Stop using `retainedTypes:` by default (only for -gfull, etc.).
>
> - Avoid blowing up memory in -flto=full (which converting MDString
> references back to pointers would do naively, through
> re-introducing cycles). Note that this needs to be handled
> somehow at BitcodeReader time.
>
> After chatting with Eric, I do...
2016 Apr 15
2
[RFC] Lazy-loading of debug info metadata
...t; The essential things I want to accomplish with this part:
> >
> > - Make `type:` operands less special: instead of referencing types
> > indirectly through MDString, point directly at the type node.
> >
> > - Stop using `retainedTypes:` by default (only for -gfull, etc.).
> >
> > - Avoid blowing up memory in -flto=full (which converting MDString
> > references back to pointers would do naively, through
> > re-introducing cycles). Note that this needs to be handled
> > somehow at BitcodeReader time.
> >
>...
2016 Mar 23
2
[RFC] Lazy-loading of debug info metadata
On Tue, Mar 22, 2016 at 8:04 PM David Blaikie <dblaikie at gmail.com> wrote:
> +pcc, who had some other ideas/patch out for improving memory usage of
> debug info
> +Reid, who's responsible for the windows/CodeView/PDB debug info which is
> motivating some of the ideas about changes to type emission
>
>
So I discussed this with Adrian and Mehdi at the social last
2016 Apr 15
2
[RFC] Lazy-loading of debug info metadata
...want to accomplish with this part:
> > >
> > > - Make `type:` operands less special: instead of referencing types
> > > indirectly through MDString, point directly at the type node.
> > >
> > > - Stop using `retainedTypes:` by default (only for -gfull, etc.).
> > >
> > > - Avoid blowing up memory in -flto=full (which converting MDString
> > > references back to pointers would do naively, through
> > > re-introducing cycles). Note that this needs to be handled
> > > somehow at BitcodeRea...
2016 May 06
2
RFC: metadata attachments for global variables
> On May 6, 2016, at 3:17 PM, Adrian Prantl <aprantl at apple.com> wrote:
>
>
>> On May 6, 2016, at 1:17 PM, Peter Collingbourne via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> 1) Lets us reverse the DIGlobalVariable -> GlobalVariable edge, which should hopefully clear the way for removing the llvm.dbg.cu named metadata node.
>
> Not to spoil all
2016 Apr 16
4
[RFC] Lazy-loading of debug info metadata
...this part:
> > > >
> > > > - Make `type:` operands less special: instead of referencing types
> > > > indirectly through MDString, point directly at the type node.
> > > >
> > > > - Stop using `retainedTypes:` by default (only for -gfull, etc.).
> > > >
> > > > - Avoid blowing up memory in -flto=full (which converting MDString
> > > > references back to pointers would do naively, through
> > > > re-introducing cycles). Note that this needs to be handled
> > > >...
2016 Apr 18
1
[RFC] Lazy-loading of debug info metadata
...> > >
>> > > > - Make `type:` operands less special: instead of referencing types
>> > > > indirectly through MDString, point directly at the type node.
>> > > >
>> > > > - Stop using `retainedTypes:` by default (only for -gfull, etc.).
>> > > >
>> > > > - Avoid blowing up memory in -flto=full (which converting MDString
>> > > > references back to pointers would do naively, through
>> > > > re-introducing cycles). Note that this needs to be handled
>...