Displaying 4 results from an estimated 4 matches for "__zn4llvm11basicaastubev".
2006 Mar 22
0
[LLVMdev] Circular dependencies
...deally, none of the above should depend on libLLVMTransformUtils.
Yeah, I'm definitely having headaches with LLVMTransformUtils, which
needs to appear before LLVMAnalysis and lLLVMTarget.
-lLLVMTransformUtils -lLLVMAnalysis -lLLVMTarget
If I don't do this, I get link errors on:
__ZN4llvm11BasicAAStubEv
I think, for now, the only portable workaround is for me to link all
the *.a libraries in that loop twice, and hope we can clean up the
dependencies later.
There's several places where llvm-config could be simplified quite a
bit if we broke the unnecessary dependencies and merged the re...
2006 Mar 22
2
[LLVMdev] Circular dependencies
...bLLVMTransformUtils.
>
> Yeah, I'm definitely having headaches with LLVMTransformUtils, which
> needs to appear before LLVMAnalysis and lLLVMTarget.
>
> -lLLVMTransformUtils -lLLVMAnalysis -lLLVMTarget
>
> If I don't do this, I get link errors on:
>
> __ZN4llvm11BasicAAStubEv
>
> I think, for now, the only portable workaround is for me to link all
> the *.a libraries in that loop twice, and hope we can clean up the
> dependencies later.
>
> There's several places where llvm-config could be simplified quite a
> bit if we broke the unneces...
2006 Mar 22
0
[LLVMdev] Circular dependencies
...h, I'm definitely having headaches with LLVMTransformUtils, which
> > needs to appear before LLVMAnalysis and lLLVMTarget.
> >
> > -lLLVMTransformUtils -lLLVMAnalysis -lLLVMTarget
> >
> > If I don't do this, I get link errors on:
> >
> > __ZN4llvm11BasicAAStubEv
> >
> > I think, for now, the only portable workaround is for me to link all
> > the *.a libraries in that loop twice, and hope we can clean up the
> > dependencies later.
> >
> > There's several places where llvm-config could be simplified quite a
&g...
2006 Mar 22
5
[LLVMdev] Circular dependencies
On Tue, 21 Mar 2006, Reid Spencer wrote:
> About the only thing I can suggest are:
>
> 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already
> happening with the new Sparc backend that is being developed. Should be
> out in 1.7 (Chris?)
I wouldn't worry about the SparcV9 backend for your project.
> 2. Combine the JIT/Interpreter/ExecutionEngine into one .a