search for: finalfile

...it being after a foreign symbol table. This > ensures > // compatibility with other ar(1) implementations as well as > allowing the > // archive to store both native .o and LLVM .bc files, both > indexed. > if (foreignST) { > writeMember(*foreignST, FinalFile, false, false, false); > } So I tracked back the foreignST pointer, and when it is set the "data" pointer is *not* 46 null bytes. It is valid data mmap-ed from the archive file. But when it gets to the call to writeMember, that data pointer is no longer valid. Running "s...

Hi, my friends I finally insert the callInst into the hello.bc file.Then I compile the hello.bc to hello.o file and the check.c to check.o file. And I think by link those to .o file togetherI can get the executable ELF file(clang hello.o check.o -o finalfile). But when I link the two objective file, it said "hello.o: In function `main': hello.bc:(.text+0x69): undefined reference to `check' clang: error: linker command failed with exit code 1 (use -v to see invocation)" What's wrong?? To make it readable I convert the .bc file...

...t 126.com> wrote: > Hi, my friends > > I finally insert the callInst into the hello.bc file.Then I compile the > hello.bc to hello.o file and the check.c to check.o file. And I think by > link those to .o file togetherI can get the executable ELF file(clang > hello.o check.o -o finalfile). > > But when I link the two objective file, it said >  "hello.o: In function `main': > hello.bc:(.text+0x69): undefined reference to `check' > clang: error: linker command failed with exit code 1 (use -v to see > invocation)" What's wrong?? > >  To ma...

I did it !!!! YOU MADE MY DAY !!!!!!!!!!!!!!! -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-10 ------------------------------------------------------------------------------------------------------ Name: 甄凯(ZhenKai) Homepage:http://www.renren.com/262729393 Email: zhenkaixd at 126.com or 846227103 at

...bol table. This >> ensures >> // compatibility with other ar(1) implementations as well as >> allowing the >> // archive to store both native .o and LLVM .bc files, both >> indexed. >> if (foreignST) { >> writeMember(*foreignST, FinalFile, false, false, false); >> } > > > So I tracked back the foreignST pointer, and when it is set the "data" > pointer is *not* 46 null bytes. It is valid data mmap-ed from the > archive file. But when it gets to the call to writeMember, that data > pointer...