search for: vfuncid

...!17 ^3 {For CFI data structures, the format would be similar. It appears that TypeIds are referred to by string name in the top level TypeIdMap (std::map indexed by std::string type identifier), whereas they are referenced by GUID within the FunctionSummary class (i.e. the TypeTests vector and the VFuncId structure). For the LLVM assembly I think there should be a top level entry for each TypeIdMap, which lists both the type identifier string and its GUID (followed by its associated information stored in the map), and the TypeTests/VFuncId references on the FunctionSummary entries can reference it b...

...tures, the format would be similar. It appears that TypeIds are >> referred to by string name in the top level TypeIdMap (std::map indexed by >> std::string type identifier), whereas they are referenced by GUID within >> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >> structure). For the LLVM assembly I think there should be a top level entry >> for each TypeIdMap, which lists both the type identifier string and its >> GUID (followed by its associated information stored in the map), and the >> TypeTests/VFuncId references on the Functi...

...a > structures, the format would be similar. It appears that TypeIds are > referred to by string name in the top level TypeIdMap (std::map indexed by > std::string type identifier), whereas they are referenced by GUID within > the FunctionSummary class (i.e. the TypeTests vector and the VFuncId > structure). For the LLVM assembly I think there should be a top level entry > for each TypeIdMap, which lists both the type identifier string and its > GUID (followed by its associated information stored in the map), and the > TypeTests/VFuncId references on the FunctionSummary entrie...

...ormat would be similar. It appears that TypeIds are >>> referred to by string name in the top level TypeIdMap (std::map indexed by >>> std::string type identifier), whereas they are referenced by GUID within >>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>> structure). For the LLVM assembly I think there should be a top level entry >>> for each TypeIdMap, which lists both the type identifier string and its >>> GUID (followed by its associated information stored in the map), and the >>> TypeTests/VFuncId referenc...

...It appears that TypeIds are >>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>> std::string type identifier), whereas they are referenced by GUID within >>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>> GUID (followed by its associated information stored in the map), and the >>>&gt...

...be similar. It appears that TypeIds are >>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>> std::string type identifier), whereas they are referenced by GUID within >>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>> structure). For the LLVM assembly I think there should be a top level entry >>>> for each TypeIdMap, which lists both the type identifier string and its >>>> GUID (followed by its associated information stored in the map), and the >>>> TypeTests/...

...be similar. It appears that TypeIds are >>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>> std::string type identifier), whereas they are referenced by GUID within >>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>> structure). For the LLVM assembly I think there should be a top level entry >>>> for each TypeIdMap, which lists both the type identifier string and its >>>> GUID (followed by its associated information stored in the map), and the >>>> TypeTests/...

...a > structures, the format would be similar. It appears that TypeIds are > referred to by string name in the top level TypeIdMap (std::map indexed by > std::string type identifier), whereas they are referenced by GUID within > the FunctionSummary class (i.e. the TypeTests vector and the VFuncId > structure). For the LLVM assembly I think there should be a top level entry > for each TypeIdMap, which lists both the type identifier string and its > GUID (followed by its associated information stored in the map), and the > TypeTests/VFuncId references on the FunctionSummary entrie...

...tures, the format would be similar. It appears that TypeIds are >> referred to by string name in the top level TypeIdMap (std::map indexed by >> std::string type identifier), whereas they are referenced by GUID within >> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >> structure). For the LLVM assembly I think there should be a top level entry >> for each TypeIdMap, which lists both the type identifier string and its >> GUID (followed by its associated information stored in the map), and the >> TypeTests/VFuncId references on the Functi...

...t; > For CFI data structures, the format would be similar. It appears that TypeIds are referred to by string name in the top level TypeIdMap (std::map indexed by std::string type identifier), whereas they are referenced by GUID within the FunctionSummary class (i.e. the TypeTests vector and the VFuncId structure). For the LLVM assembly I think there should be a top level entry for each TypeIdMap, which lists both the type identifier string and its GUID (followed by its associated information stored in the map), and the TypeTests/VFuncId references on the FunctionSummary entries can reference it b...

...a > structures, the format would be similar. It appears that TypeIds are > referred to by string name in the top level TypeIdMap (std::map indexed by > std::string type identifier), whereas they are referenced by GUID within > the FunctionSummary class (i.e. the TypeTests vector and the VFuncId > structure). For the LLVM assembly I think there should be a top level entry > for each TypeIdMap, which lists both the type identifier string and its > GUID (followed by its associated information stored in the map), and the > TypeTests/VFuncId references on the FunctionSummary entrie...

...ormat would be similar. It appears that TypeIds are >>> referred to by string name in the top level TypeIdMap (std::map indexed by >>> std::string type identifier), whereas they are referenced by GUID within >>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>> structure). For the LLVM assembly I think there should be a top level entry >>> for each TypeIdMap, which lists both the type identifier string and its >>> GUID (followed by its associated information stored in the map), and the >>> TypeTests/VFuncId referenc...

...hat TypeIds are >>>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>> GUID (followed by its associated information stored in the map), and the &gt...

...are >>>>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>>> GUID (followed by its associated information stored in the map),...

...>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>>>>> GUID (followed by its associated informa...

...>>>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>>>> GUID (followed by its associated information stored...

...>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>>>>>> GUID (followed by its associ...

...>> For CFI data structures, the format would be similar. It appears that TypeIds are referred to by string name in the top level TypeIdMap (std::map indexed by std::string type identifier), whereas they are referenced by GUID within the FunctionSummary class (i.e. the TypeTests vector and the VFuncId structure). For the LLVM assembly I think there should be a top level entry for each TypeIdMap, which lists both the type identifier string and its GUID (followed by its associated information stored in the map), and the TypeTests/VFuncId references on the FunctionSummary entries can reference it b...

...t; > For CFI data structures, the format would be similar. It appears that TypeIds are referred to by string name in the top level TypeIdMap (std::map indexed by std::string type identifier), whereas they are referenced by GUID within the FunctionSummary class (i.e. the TypeTests vector and the VFuncId structure). For the LLVM assembly I think there should be a top level entry for each TypeIdMap, which lists both the type identifier string and its GUID (followed by its associated information stored in the map), and the TypeTests/VFuncId references on the FunctionSummary entries can reference it b...

...>>>>>> referred to by string name in the top level TypeIdMap (std::map indexed by >>>>>>>> std::string type identifier), whereas they are referenced by GUID within >>>>>>>> the FunctionSummary class (i.e. the TypeTests vector and the VFuncId >>>>>>>> structure). For the LLVM assembly I think there should be a top level entry >>>>>>>> for each TypeIdMap, which lists both the type identifier string and its >>>>>>>> GUID (followed by its associated information stored...