Displaying 2 results from an estimated 2 matches for "r183830".
2013 Jun 12
2
[LLVMdev] "anchor" method policy, request for clarification
....o:(.data.rel.ro._ZTIN4llvm2cl15OptionValueCopyINS0_13boolOrDefaultEEE[_ZTIN4llvm2cl15OptionValueCopyINS0_13boolOrDefaultEEE]+0x10): undefined reference to `typeinfo for llvm::cl::GenericOptionValue'
This seems to be due to the (mis-)use of "anchor" methods in CommandLine. I commited r183830, with a removal of the anchor method for GenericOptionValue, which solved my link problem. Also, the commit didn't change the number of vtables, as measured by:
find -name \*.o | xargs nm -C | grep 'V vtable' | grep OptionValue | wc
The current LLVM developer policy text regarding &q...
2013 Jun 12
0
[LLVMdev] "anchor" method policy, request for clarification
...the misuse you have in mind? Can you explain why the anchor
wasn't being linked in? It sounds like the unit test wasn't linking to
all the libs it should've been. (& that removing the anchor was simply
a workaround to avoid linking to an implementation file...)
> I
> commited r183830, with a removal of the anchor method for
> GenericOptionValue, which solved my link problem. Also, the commit didn’t
> change the number of vtables, as measured by:
>
>
>
> find -name \*.o | xargs nm -C | grep 'V vtable' | grep OptionValue | wc
Where did you run this comm...