Lines Matching refs:RTTI
340 /**************************** RTTI Uniqueness ******************************/
343 /// Returns true if the ABI requires RTTI type_info objects to be unique
348 /// What sort of unique-RTTI behavior should we use?
350 /// We are guaranteeing, or need to guarantee, that the RTTI string
354 /// We are not guaranteeing uniqueness for the RTTI string, so we
358 /// We are not guaranteeing uniqueness for the RTTI string, so we
438 // ARM64 libraries are prepared for non-unique RTTI.
1464 llvm::Constant *RTTI =
1470 VTLayout.vtable_thunk_begin(), VTLayout.getNumVTableThunks(), RTTI);
2353 /// Fields - The fields of the RTTI descriptor currently being built.
2360 /// GetAddrOfExternalRTTIDescriptor - Returns the constant for the RTTI
2429 /// BuildTypeInfo - Build the RTTI type info struct for the given type.
2431 /// \param Force - true to force the creation of this RTTI value
2458 // Mangle the RTTI name.
2595 // If RTTI is disabled, assume it might be disabled in the
2597 if (!Context.getLangOpts().RTTI) return false;
2609 // N.B. We must always emit the RTTI data ourselves if there exists a key
2820 // by making them local static objects. Finally, a dummy class RTTI is
2822 // complete class RTTI (because the latter need not exist), possibly by
2835 if (!CGM.getLangOpts().RTTI) {
2836 // RTTI is not enabled, which means that this type info struct is going
2847 // MinGW won't export the RTTI information when there is a key function.
2866 // Check if we've already emitted an RTTI descriptor for this type.
2879 // Check if there is already an external RTTI descriptor for this type.
3024 // of RTTI generally require class types to be complete, even when
3202 // The __base_type member points to the RTTI for the base type.
3341 /// What sort of uniqueness rules should we use for the RTTI for the
