Displaying 3 results from an estimated 3 matches for "847a4f00".
Did you mean:
4754f00
2013 Sep 24
0
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
I think having this would be awesome!
On Tue, Sep 24, 2013 at 4:11 AM, Anders Waldenborg <anders at 0x63.nu> wrote:
> On Mon, Sep 23, 2013 at 07:48:45PM -0400, Sean Silva wrote:
>> I like the idea, but I find the name confusing; I think it should have
>> `llvm-c` or `c-api` somewhere in the name. This could also serve as a
>> simple example of using the API.
>
> I
2013 Sep 24
2
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
On Mon, Sep 23, 2013 at 07:48:45PM -0400, Sean Silva wrote:
> I like the idea, but I find the name confusing; I think it should have
> `llvm-c` or `c-api` somewhere in the name. This could also serve as a
> simple example of using the API.
I had it as llvm-c-test first, then noticed that the shared library's
directory was named "llvm-shlib".
Yes, making sure it serves as
2013 Sep 30
1
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
...case. (also the dup2 use, will
that work on windows?).
Thanks
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm-c-test-r2.patch
Type: text/x-diff
Size: 30807 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130930/847a4f00/attachment.patch>