[PATCH] D45244: Add missing vtable anchors

David Blaikie via llvm-commits llvm-commits at lists.llvm.org
Mon Apr 9 12:00:47 PDT 2018


Looks like ObjectMemoryBuffer is part of ExecutionEngine, so having libLTO
dependent on ExecutionEngine seems basically correct for the dependencies
that are there already. Whether or not those dependencies should be there
is another question, I guess. (maybe ObjectMemoryBuffer should be moved
somewhere more common, etc - but I wouldn't worry about doing that unless
the LTO dependency breaks things)

On Wed, Apr 4, 2018 at 12:43 AM Weiming Zhao via Phabricator via
llvm-commits <llvm-commits at lists.llvm.org> wrote:

> weimingz added a comment.
>
> When I statically linking a project (built with RTTI) against LLVM OrcJIT
> (default built with no-RTTI), I got a couple of "undefined reference to
> type info" error.
>
> Looks similar to
> http://lists.llvm.org/pipermail/llvm-dev/2016-February/095671.html
>
> However, I'm not sure where to put the definition of anchor() for
> ObjectMemoryBuffer class. It's used by ThinLTOCodeGenerator.cpp and
> MCJIT.cpp, which belong to different libs.
>
>
> Repository:
>   rL LLVM
>
> https://reviews.llvm.org/D45244
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20180409/f7a79d70/attachment.html>


More information about the llvm-commits mailing list