Embedded Bitcode in Object Files
Steven Wu via llvm-commits
llvm-commits at lists.llvm.org
Tue Nov 29 13:57:31 PST 2016
Thanks for reviewing the patches. And yes, 3 and 4 are no longer useful. I am seeking better alternatives to achieve them.
Steven
> On Nov 30, 2016, at 1:35 AM, Nico Weber <thakis at chromium.org> wrote:
>
> It looks like patches 1 and 2 made it but 3 and 4 didn't. Do you no longer need them?
>
>> On Mon, Feb 29, 2016 at 2:08 PM, Steven Wu via cfe-commits <cfe-commits at lists.llvm.org> wrote:
>> Ping. I don't know who is the best review for the patches. Thanks for Rafael looking at the LLVM change. Richard, do you have any opinions on the clang changes?
>>
>> Thanks
>>
>> Steven
>>
>> > On Feb 18, 2016, at 9:57 AM, Steven Wu <stevenwu at apple.com> wrote:
>> >
>> > Hi all
>> >
>> > I put up some patches for embedding bitcode inside the object file (-fembed-bitcode) option. As I described in the dev list before, the new option can create normal object file with bitcode embedded in a special section. You can easily recreate the same object file with the embedded bitcode in it.
>> >
>> > I split the patch into several parts:
>> > llvm patch:
>> > http://reviews.llvm.org/D17388: Introduce the section for embedding bitcode in MachO file.
>> >
>> > There are four clang patches:
>> > http://reviews.llvm.org/D17390: Implementing the clang driver for the new option.
>> > http://reviews.llvm.org/D17392: Teach clang how to embed bitcode into the object file.
>> > http://reviews.llvm.org/D17393: Slightly tweak the bitcode emitted in embed bitcode stage 1.
>> > http://reviews.llvm.org/D17394: Reduce the amount of option gets embedded in the bitcode by introducing a whitelist and a blacklist.
>> >
>> > Let me know if anyone is interested in helping reviewing these changes.
>> >
>> > Thanks
>> >
>> > Steven
>> >
>> >
>> >
>>
>> _______________________________________________
>> cfe-commits mailing list
>> cfe-commits at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20161130/46535c76/attachment.html>
More information about the llvm-commits
mailing list