Displaying 3 results from an estimated 3 matches for "7fc6b7f5".
2008 Feb 26
2
[LLVMdev] new LTO C interface
...> Existing bindings use the term dispose to avoid any possible retain/
> release confusion.
Changed both _release functions to _dispose.
-Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080225/7fc6b7f5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lto.h
Type: application/octet-stream
Size: 6597 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080225/7fc6b7f5/attachment.obj>
-------------- next pa...
2008 Feb 25
0
[LLVMdev] new LTO C interface
Hi Nick,
I don't have any comments on the substance of the APIs (I'm not expert
in this area), just some style notes. Overall, the capitalization
style is inconsistent with the bulk of the C bindings, which are more
Carbon than GNU.
On Feb 23, 2008, at 01:34, Nick Kledzik wrote:
> #include <stdint.h>
> #include <stdbool.h>
Note that MSVC++ still doesn't
2008 Feb 23
5
[LLVMdev] new LTO C interface
Hello. I work at Apple on our linker. We are working to improve
support for llvm
in our tools. A while back Devang created <llvm/LinkTimeOptimizer.h>
a C++
interface which allows the linker to process llvm bitcode files along
with native
mach-o object files.
For the next step we'd like our other tools like nm, ar, and lipo to
be able to
transparently process bitcode files