[llvm] r180229 - Exposing MCJIT through C API

[Filip Pizlo]

Well, I guess it accomplishes nothing; I guess I was confused.  I thought that whether the first virtual method was inline or out-of-line had an impact on the linkage of the vtable, and that this was the problem.

-Filip


On Apr 26, 2013, at 3:22 PM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote:

> I don’t think I see what this anchor is supposed to accomplish.  There are already virtual methods from SectionMemoryManager that are defined in SectionMemoryManager.cpp.  What does the anchor function add?
>  
> -Andy
>  
>  
> From: Filip Pizlo [mailto:fpizlo at apple.com] 
> Sent: Friday, April 26, 2013 1:24 PM
> To: llvm-commits
> Cc: Kaylor, Andrew; edwintorok at gmail.com; Rafael Espíndola
> Subject: Re: [llvm] r180229 - Exposing MCJIT through C API
>  
> I suspect that the build error is due to a lack of an anchor, causing some builds to think that the vtable for SectionMemoryManager is somewhere that it isn't.  New patch, if y'all are fine with a speculative fix:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130426/e2c80073/attachment.html>