Lines Matching refs:profile

12  * defined in this file affect the profile runtime ABI, the raw profile format,
16 * the other one sits in compiler-rt/lib/profile directory. To make changes
83 * function name hashes during the conversion from raw to merged profile
146 /* Definition of member fields of the raw profile header data structure. */
148 raw profile format. */
202 * written in the raw profile data and converted to target function name's MD5
203 * hash by the profile reader during deserialization. Typically, this happens
204 * when the raw profile data is read during profile merging.
217 * The profiled addresses are stored in raw profile, together with the following
359 * layout of the value profile data of a particular kind for one function.
362 /* The kind of the value profile record. */
365 * The number of value profile sites. It is guaranteed to be non-zero;
383 /* The array of value profile data. The size of the array is the sum
418 *The number of value profile kinds that has value profile data.
419 * In this implementation, a value profile kind is considered to
420 * have profile data if the number of value profile sites for the
437 * Return the total size in bytes of the on-disk value profile data
481 * The closure is designed to abstact away two types of value profile data:
483 * represent profile data in host tools (reader, writer, and profile-use)
484 * - value profile runtime data structure suitable to be used by C
489 * writer to share the same format and code with indexed profile writer.
502 * After extracting the value profile data from the value profile record,
555 * Return the total size of the value profile record including the
607 * Return the total size in bytes of the on-disk value profile data
627 * Extract value profile data of a function for the profile kind \c ValueKind
649 * Extract value profile data of a function from the \c Closure
710 /* Raw profile format version (start from 1). */
712 /* Indexed profile format version (start from 1). */
718 * version for other variants of profile. We set the 8th most significant bit
720 * generated profile, and 0 if this is a Clang FE generated profile.
721 * 1 in bit 57 indicates there are context-sensitive records in the profile.
725 * The 62nd bit indicates whether memory profile information is present.
726 * The 63rd bit indicates if this is a temporal profile.
744 /* The variable that holds the name of the profile data
795 /* Value profile nodes section. */
814 /* Value profile nodes section. */
912 * range and used to store in the runtime profile data records and the VP