Displaying 3 results from an estimated 3 matches for "tp33259763p33262186".
2012 Feb 03
2
[LLVMdev] Invalid bitcode signature
I'm trying to link two modules together using the C++ API, one that's a sort
of library module and one that's being generated from the source language.
If I have something like this:
OwningPtr<MemoryBuffer> owning_ptr;
if (MemoryBuffer::getFile(StringRef("../hello.bc"), owning_ptr))
std::cout << "error opening file" << std::endl;
Module* Lib
2012 Feb 04
0
[LLVMdev] Invalid bitcode signature
On Feb 3, 2012, at 1:47 PM, Fraser Cormack wrote:
>
> I'm trying to link two modules together using the C++ API, one that's a sort
> of library module and one that's being generated from the source language.
>
> If I have something like this:
>
> OwningPtr<MemoryBuffer> owning_ptr;
> if (MemoryBuffer::getFile(StringRef("../hello.bc"),
2012 Feb 04
2
[LLVMdev] Invalid bitcode signature
...bit-code file, not the text version.
>
> And, llvm-gcc? really? :-)
>
>
Is there no way that the API can generate valid bitcode?
And no, not really llvm-gcc, I'm not sure why I said that, haha :)
--
View this message in context: http://old.nabble.com/Invalid-bitcode-signature-tp33259763p33262186.html
Sent from the LLVM - Dev mailing list archive at Nabble.com.