[llvm-dev] -fno-rtti compilation option

David Chisnall via llvm-dev llvm-dev at lists.llvm.org
Wed Dec 2 07:22:49 PST 2015

On 2 Dec 2015, at 15:20, Adrien DEGRANGE via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> This sounds annoying… Has anyone already encountered such an issue? How did you manage with that?

I found this issue, but it was too late to get a fix in to 3.7.  The issue is that a number of classes in public headers don’t have an anchor method and so get emitted in every compilation unit, and their vtable refers to the type_info in the superclass (if that compilation unit has RTTI enabled), which doesn’t exist.

The work-around that we use is to build LLVM with RTTI enabled.


More information about the llvm-dev mailing list