Displaying 2 results from an estimated 2 matches for "46e4db36".
2016 Mar 30
0
[cfe-dev] RFC: Up front type information generation in clang and llvm
...ing. Then we can have all of the type information for a single translation unit in a single blob and use the debug aware linking to handle merging types.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160330/46e4db36/attachment-0001.html>
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