search for: symol

...which consists of 1000's of functions spread through various files. The functions do not have dependency amoung each other. I want to link only relavant files( files which have functions called from my application). Since ar has a global symbol table, I believe it should be faster to look for a symol in the table and pull out and link the file to .bc of my application. Is my understand regarding llvm-ar correct? Or is there a better way to achieve it? One not-so-great solution I can think of is compile the library into separate .bc files and write llvm pass which has a predefined hash mapping...

Hi Ankur, Why do you need archive in this case? The other way of doing this is to merge all bitcode files into single file: $ clang -c -emit-llvm abc.c -o abc.bc $ clang -c -emit-llvm bcd.c -o bcd.bc llvm-link bcd.bc abc.bc -o merged.bc Cheers, Ahmad From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of ankur deshwal Sent: 21 February 2013 17:54 To:

Hi, I tried to build an llvm archive and link it against an llvm bc file. However, it fails. Following is the procedure I followed ( abc.c is file which calls a function whose definition is present in bcd.c) $ clang -c -emit-llvm abc.c $ clang -c -emit-llvm bcd.c $ llvm-ar cr bsd.ar bcd.o $ llvm-link abc.o bsd.ar llvm-link: bsd.ar:1:2: error: expected integer !<arch> ^ llvm-link:

I compiled and installed pyogg followed by pyvorbis, running: $ ./config_unix.py $ python setup.py build and as root: # python setup.py install for pyogg and pyvorbis in turn. This completed without error, however upon trying to import ogg.vorbis in IDLE I get an import error: ImportError: libvorbisfile.so.3: cannot open shared object file: No such file or directory I was told this may have

I don't know who this problem belongs to, samba or Linux, but it's a common one, judging by the responses in my INBOX to a previous post. Plus, it's a fairly serious one; many applications require smb shares to be mounted continuously and without interruption. It's been a recurring problem which seems to have been pushed off to the side as not important, even though it's a

...h for it to become free. Though actually it was free! Now, here is one issue I have in understanding the dump: the back traces produced in crash are in the normal form not showing any cpu in the poll_irq HV call. Only when using the form that uses the last known stack location and displays all text symols found will get close for cpu#7. cpu#0 still does not seem to be anywhere close. This could be a problem with crash, or with the way PVM works, I am not sure. Anyway, from what I could take from that situation, it seemed that cpu#1 (that one had soft lockup warnings in the log) seemed to try to do...