search for: myprintf

Hi Rui, I thought about this, but there is a catch. The undefined symbols still need to be resolved with exports from dynamic libraries even the second time, or any number of times. For example :- ld 1.o --start-group libc.so myprintf.a --end-group 1.o has a undef for myprintf, which is in myprintf.a and myprintf.a calls puts. The first time when libc.so, undef atoms would be added, no shared library export atoms would be created because there is nothing that libc.so would resolve. The second time, undefined symbols from s...

I'd do that with the nextFile abstraction like this: On the first iteration, a Group would return its member every time getNextFile() is called (the same as the current behavior). On the second and further iterations, the Group should skip all the members whose type is not Archive. By doing this, the core linker sees dynamic libraries (or regular object files) only once even if they are in

...s a standard c function like "printf", can anyone help me with this problem? The file attached is the program I wrote, it can be compiled, however, the result of the dump of the retrieved module is not correct(missing global variable and will cause 'program use external function 'myprintf' which could not be resolved') problem. http://old.nabble.com/file/p27210247/test.cpp test.cpp -- View this message in context: http://old.nabble.com/How-to-create-a-CallInst-that-calls-a-standard-c-function-like-%22printf%22-tp27210247p27210247.html Sent from the LLVM - Dev mailing list...

Hi Nick, --start-group/--end-group functionality with the Gnu flavor currently works only if the --start-group/--end-group contains archive files. If they contain dynamic libraries, the undefined atoms from the dynamic libraries are processed whenever the group is iterated again. I am trying to find out a way to make the resolver add undefined atoms from the shared library only *once*, when

...ike "printf", can anyone help > me with this problem? > > The file attached is the program I wrote, it can be compiled, however, the > result of the dump of the retrieved module is not correct(missing global > variable and will cause 'program use external function 'myprintf' which > could not be resolved') problem. > http://old.nabble.com/file/p27210247/test.cpp test.cpp > :-) -- View this message in context: http://old.nabble.com/How-to-create-a-CallInst-that-calls-a-standard-c-function-like-%22printf%22-tp27210247p27258957.html Sent from the LLV...

Hello all, I just got the latest cvs snapshot and I'm trying to compile asterisk.. When I run nefeli:/usr/src/asterisk/zaptel# make clean; make linux26 Compile stops with errors... /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing argument 2 of 'class_device_create' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing argument 3

...lt-in functions like printf() when the bitcode is loaded. I'm supposing something along the lines of a Linker::ItemList may exist somewhere which provides names and addresses of built-in functions(?) On a related note, I'm wondering how one would make one's own built-in functions like myprintf() or such, available so that bitcode, when loaded, could link with them? (Apologies if this is an RTFM.) Thanks for any help, Bill

...itcode is > loaded. > > I'm supposing something along the lines of a > Linker::ItemList may exist somewhere which provides > names and addresses of built-in functions(?) > > On a related note, I'm wondering how one would make > one's own built-in functions like myprintf() or such, > available so that bitcode, when loaded, could link > with them? > > (Apologies if this is an RTFM.) > > > Thanks for any help, > > Bill > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.ed...

Hi list, I have several questions about LLVM pass. 1) Is building a custom LLVM pass out-of-source not recommended? The official document only contains instructions about in-source build (http://llvm.org/docs/WritingAnLLVMPass.html <http://llvm.org/docs/WritingAnLLVMPass.html>). 2) opt (ver >= 4) with custom pass libraries does not work as before. When I have a simple custom LLVM pass