Displaying 3 results from an estimated 3 matches for "d19236".
2016 Apr 27
2
RFC: Up front type information generation in clang and llvm
...forward declaration of composite types.
>
> In the future, when we do this work for DWARF, we can add a new DIType*
> stand-in similar to what you are describing.
>
> The working patch that I have for just CodeView, all types as a single
> blob, is up here: http://reviews.llvm.org/D19236 While it doesn't deal
> with type blobs or LTO type merging yet, I think it shows that there is
> surprisingly little need to bifurcate other parts of LLVM.
>
> Thoughts?
>
> On Tue, Mar 29, 2016 at 6:00 PM, Eric Christopher <echristo at gmail.com>
> wrote:
>
>&...
2016 May 11
2
RFC: Up front type information generation in clang and llvm
...declaration of composite types.
>>
>> In the future, when we do this work for DWARF, we can add a new DIType* stand-in similar to what you are describing.
>>
>> The working patch that I have for just CodeView, all types as a single blob, is up here: http://reviews.llvm.org/D19236 <http://reviews.llvm.org/D19236> While it doesn't deal with type blobs or LTO type merging yet, I think it shows that there is surprisingly little need to bifurcate other parts of LLVM.
>>
>> Thoughts?
>>
>> On Tue, Mar 29, 2016 at 6:00 PM, Eric Christopher <e...
2016 Mar 30
14
RFC: Up front type information generation in clang and llvm
Hi All,
This is something that's been talked about for some time and it's probably
time to propose it.
The "We" in this document is everyone on the cc line plus me.
Please go ahead and take a look.
Thanks!
-eric
Objective (and TL;DR)
=================
Migrate debug type information generation from the backends to the front
end.
This will enable:
1. Separation of