search for: llvm_link

...my original question. Now I'm actually moving a step further. Take the same example in your reply, say, if I have a bunch of .c files, where a.c calls functions defined in b.c, b.c calls functions defined in c.c and so on. I know that I can compile them into a .bc file by using this command: ~/llvm_link -I <HEADER_DIR> a.c b.c c.c d.c -emit-llvm -c -o linked.bc But the problem is all of the files which define the callees need to be specified manually. Is it possible that the source files in which the callees are defined can be automatically inferred, compiled and linked? If so, then we can...

Hi Johannes, By following your directions, I can use your script as is to produce the .bc file now. Here's my command line for compiling s_sin.c into s_sin.bc file and the output: command line: ~/Downloads/newlib-2.1.0/newlib/libm/mathfp » python ~/llvm_link.py s_sin.c -I../common/ -I../../libc/include/ -o s_sin.bc output: Initiate CLANG (/path-to-clang): Options: 's_sin.c -I../common/ -I../../libc/include/ -o s_sin.bc -emit-llvm -c' In file included from s_sin.c:18: ./zmath.h:7:9: warning: 'NAN' macro redefined #define NAN 2...

Good tips. Although I have used llvm-link to merge .bc files together, I guess -flto could optimize the resultant .bc file further. As for the assembly, yes it is an issue. Anyway, I'll try to address those sources which are available for being translated into .bc first. Thanks for your advice, Tim. On Mon, Sep 15, 2014 at 2:55 PM, Tim Northover <t.p.northover at gmail.com> wrote:

This was replaced by having a #<num> referenced by the object. Kind of like how metadata is referenced. -bw On Feb 3, 2013, at 4:50 PM, Sean Silva <silvas at purdue.edu> wrote: >> To use an attribute group, an object references the attribute group's ID: >> >> attribute_group_ref := attrgroup(<attrgroup_id>) > > Is this unused now? I don't see