Lines Matching defs:RTTI
394 /**************************** RTTI Uniqueness ******************************/
397 /// Returns true if the ABI requires RTTI type_info objects to be unique
402 /// What sort of unique-RTTI behavior should we use?
404 /// We are guaranteeing, or need to guarantee, that the RTTI string
408 /// We are not guaranteeing uniqueness for the RTTI string, so we
412 /// We are not guaranteeing uniqueness for the RTTI string, so we
511 // ARM64 libraries are prepared for non-unique RTTI.
2001 llvm::Constant *RTTI =
2007 CGVT.createVTableInitializer(components, VTLayout, RTTI,
3428 /// Fields - The fields of the RTTI descriptor currently being built.
3435 /// GetAddrOfExternalRTTIDescriptor - Returns the constant for the RTTI
3510 /// BuildTypeInfo - Build the RTTI type info struct for the given type, or
3511 /// link to an existing RTTI descriptor if one already exists.
3514 /// BuildTypeInfo - Build the RTTI type info struct for the given type.
3546 // Mangle the RTTI name.
3557 // RTTI, check if emitting vtables opportunistically need any adjustment.
3590 // GCC also emits RTTI for __int128.
3591 // FIXME: We do not emit RTTI information for decimal types here.
3733 // If RTTI is disabled, assume it might be disabled in the
3735 if (!Context.getLangOpts().RTTI) return false;
3747 // N.B. We must always emit the RTTI data ourselves if there exists a key
3751 // Don't import the RTTI but emit it locally.
4004 // by making them local static objects. Finally, a dummy class RTTI is
4006 // complete class RTTI (because the latter need not exist), possibly by
4023 // RTTI is not enabled, which means that this type info struct is going
4025 if (!CGM.getLangOpts().RTTI)
4055 // Check if we've already emitted an RTTI descriptor for this type.
4068 // Check if there is already an external RTTI descriptor for this type.
4232 llvm_unreachable("HLSL doesn't support RTTI");
4270 // of RTTI generally require class types to be complete, even when
4443 // The __base_type member points to the RTTI for the base type.
4598 /// What sort of uniqueness rules should we use for the RTTI for the