https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83876
Bug ID: 83876
Summary: [feature request] flag to force vague linkage for
typeinfo and/or disable vtable anchoring
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland at rschulz dot eu
Target Milestone: ---
Vague linking is required for runtime binding [1] and RTTI to work together. If
vtable anchoring is possible, then GCC makes use of it, and doesn't use vague
linking for typeinfo. This breaks runtime binding [2]. It would be nice if GCC
could add a flag which disables vtable anchoring and/or forces vague linking
even if vtable anchoring is possible. This would enable to use runtime binding
using dlopen even if out-of-line virtual functions exist.
1)
https://stackoverflow.com/questions/29524200/how-to-do-runtime-binding-based-on-cpu-capabilities-on-linux
2)
https://stackoverflow.com/questions/48246196/virtual-exception-class-causes-dynamic-linker-error
