[LLD] Cyclic dependency between ReaderWriter and YAML backend
Shankar Easwaran
shankare at codeaurora.org
Mon Sep 2 21:28:01 PDT 2013
On 9/2/2013 11:09 PM, Chandler Carruth wrote:
> I really don't follow what you're saying. Not all linkers are capable
> of resolving cyclic references using start-group/end-group even for
> static links. Thus, I'm suggesting we shouldn't include such patterns
> in any art of our design. I don't know if it does today or not, I'm
> merely responding to your comment that cyclic dependencies could be
> handled with start-group/end-group to clarify that this isn't a viable
> solution on all platforms where LLVM projects are being built.
Sorry for being terse.
I totally agree to your point that, we shouldnot be using
--start-group/--end-group.
What I was trying to mention here is :-
a) Currently lld creates a shared library for each of the individual
components when BUILD_SHARED_LIBS is turned on.
The list of libraries are liblldYAML, liblldELF and so on.
Inorder for utilities to link with lld libraries, doesnt llvm-config
need to contain the list of lld libraries too, that the tools need
inorder to link with ?
Thanks
Shankar Easwaran
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
More information about the llvm-commits
mailing list