search for: vftable_for_type

...t float 1.0, section $.my_section, align 4 The following is how I imagine MS RTTI would look like if we had this IR construct: $.vdata_for_type = pick_largest read @my_rtti_for_type = pick_largest unnamed_addr constant %rtti_ptr_ty @rtti_complete_object_locator, section $.vdata_for_type, align 4 @vftable_for_type = pick_largest unnamed_addr constant [1 x i8*] [i8* bitcast (void (%struct.S*)* @"\01?fun at S@@UAEXXZ" to i8*)], section $.vdata_for_type, align 4 Attached is a patch to the LangRef. Thanks for reading! -------------- next part -------------- An HTML attachment was scrubbed... URL: &lt...

...s how I imagine MS RTTI would look like if we had this IR > > construct: > > > > $.vdata_for_type = pick_largest read > > @my_rtti_for_type = pick_largest unnamed_addr constant %rtti_ptr_ty > > @rtti_complete_object_locator, section $.vdata_for_type, align 4 > > @vftable_for_type = pick_largest unnamed_addr constant [1 x i8*] [i8* > > bitcast (void (%struct.S*)* @"\01?fun at S@@UAEXXZ" to i8*)], section > > $.vdata_for_type, align 4 > > Part of the problem is that it seems that the order is important. We > really should not require that at the...