search for: thingsn

...ated for each source file, an object file is created, then those (native, non-IR) object files are linked together. So it's somewhat a invalid concept. In your case, since there's only one file anyway, just add -c and you should be fine (your IR won't include the standard library/other thingsn that would be linked into the program - but those would be native objects and not IR in any case) - Dave On Mon, May 30, 2016 at 5:33 AM, Lorenzo Laneve via llvm-dev < llvm-dev at lists.llvm.org> wrote: > When I try to do > > clang++ main.cpp -emit-llvm > > without -S, clang...

When I try to do clang++ main.cpp -emit-llvm without -S, clang says that he can’t: clang: error: -emit-llvm cannot be used when linking why can’t it emit the IR in a complete compilation process? Is there a particular technical reason or just to avoid confusing jobs? -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ach source file, an object file is created, then those (native, non-IR) object files are linked together. So it's somewhat a invalid concept. > > In your case, since there's only one file anyway, just add -c and you should be fine (your IR won't include the standard library/other thingsn that would be linked into the program - but those would be native objects and not IR in any case) > > - Dave > >> On Mon, May 30, 2016 at 5:33 AM, Lorenzo Laneve via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> When I try to do >> >> clang++ main.cpp -e...

I'd like to jump in. I do not work on a preprocessor based language, but have the same code expansion problem to encode. Right now, we hack around the problem by appending some prefix after the file name and pretend it is a different file, which is not great. I understand you want to represent expansion by DIFileMacro ? I'm not how this is supposed to be used and it is not in the example.