search for: my_rtti_for_typ

...xecute, etc.) A concrete example of a const variable inside of a read-only section: $.my_section = appending read @my_var = constant 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 Attach...

...s bah, which is at offset 4. > I like this proposal. Any reason to use an explicit offset rather than allow GEPs into aliases? > 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 &gt...