search for: naclports

Displaying 5 results from an estimated 5 matches for "naclports".

Did you mean: backports
2015 Jun 24
3
[LLVMdev] how to compile a large project to LLVM IR?
...on the linker you are using, but Apple’s ld and I believe the gold linker both have -save-temps options which save the bit codes before/after optimization but certainly after linking. Cheers, Pete > > I suggest you take a look at the "NaCl ports" project (https://code.google.com/p/naclports/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__code.google.com_p_naclports_&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=RfjvEJWweAkWHLneLw1ksvf1RoobZbEIUUVtXtJgYv4&s=RvO9OeVGsfCkE0U5HJQV_pwo1s2U1qoZg2Wx-gK19cs&e=>). It has...
2015 Jun 24
3
[LLVMdev] how to compile a large project to LLVM IR?
Hello,I want to compile a large project(for example,Apache httpd) to one .bc file. How can I do this? Can you give me some examples? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150624/105789c4/attachment.html>
2011 Dec 14
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
> Is it more clear now? If not, I would like to give it another try and > write much more details and examples. I am still not completely sure I understand the use case. In particular since you say you want a bitcode module in the end, I don't understand how this is different from using llvm-link, it doesn't complain about undefined symbols... Can you provide an example? What are
2011 Dec 14
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
On Tue, Dec 13, 2011 at 9:27 PM, Rafael Ávila de Espíndola < rafael.espindola at gmail.com> wrote: > > > $ llc bar.bc -filetype=obj -o bar.o > > $ clang -shared -o bar.so bar.o > > $ clang -use-gold-plugin foo.o bar.so -o t > > > > Is that correct? In particular, "lld t" should show a dependency on > bar. > > Any
2016 May 04
9
[PATCH 0/8] python: PEP 8 fixes
Hi, this series cleans up the Python sources, either static or generated, including also tests, to make them PEP 8 compliant; see https://www.python.org/dev/peps/pep-0008/ and tools like pep8. Almost all the issues reported by pep8 are fixed, reducing the issues from 3818 to 7. The changes should have no effect on the actual code, while it will help Python users with consistency with other