Searched refs:IPR (Results 1 – 6 of 6) sorted by relevance
1099 const auto *IPR = reinterpret_cast<const InstrProfRecord *>(R); in getNumValueDataForSiteInstrProf() local1100 return IPR->getValueArrayForSite(VK, S).size(); in getNumValueDataForSiteInstrProf()1105 const auto *IPR = reinterpret_cast<const InstrProfRecord *>(R); in getValueForSiteInstrProf() local1106 llvm::copy(IPR->getValueArrayForSite(K, S), Dst); in getValueForSiteInstrProf()
416 const InstrProfRecord &IPR = Func.second; in shouldEncodeData() local417 if (llvm::any_of(IPR.Counts, [](uint64_t Count) { return Count > 0; })) in shouldEncodeData()419 if (llvm::any_of(IPR.BitmapBytes, [](uint8_t Byte) { return Byte > 0; })) in shouldEncodeData()
314 Copies of IPR disclosures made to the IETF Secretariat and any318 specification can be obtained from the IETF on-line IPR repository at
762 Copies of IPR disclosures made to the IETF Secretariat and any766 specification can be obtained from the IETF on-line IPR repository at
2353 right (IPR) restriction. KAME's stance is stated below.2358 contract with IPR holder, and (2) are royalty-free.2359 The reason for (1) is, even if KAME contracts with the IPR holder in2361 codebase) would need to make a license contract with the IPR holder.2368 is free of IPR infringement, you MUST check it if you are to integrate
4909 033d PCI-E IPR SAS Adapter (FPGA)4915 034a PCI-E IPR SAS Adapter (ASIC)4935 04da PCI-E IPR SAS+ Adapter (ASIC)