Searched refs:cumul (Results 1 – 4 of 4) sorted by relevance
103 U32 *cumul; in FSE_buildCTable_wksp() local107 cumul = (U32 *)workspace + spaceUsed32; in FSE_buildCTable_wksp()127 cumul[0] = 0; in FSE_buildCTable_wksp()130 cumul[u] = cumul[u - 1] + 1; in FSE_buildCTable_wksp()133 cumul[u] = cumul[u - 1] + normalizedCounter[u - 1]; in FSE_buildCTable_wksp()136 cumul[maxSymbolValue + 1] = tableSize + 1; in FSE_buildCTable_wksp()162 …tableU16[cumul[s]++] = (U16)(tableSize + u); /* TableU16 : sorted by symbol order; gives next stat… in FSE_buildCTable_wksp()
76 let A-cumul(r) = (rfe ; [Marked])? ; r77 let cumul-fence = [Marked] ; (A-cumul(strong-fence | po-rel) | wmb |79 let prop = [Marked] ; (overwrite & ext)? ; cumul-fence* ;170 let vis = cumul-fence* ; rfe? ; [Marked] ;
127 u64 cumul; in __callchain__fprintf_graph() local130 cumul = callchain_cumul_hits(child); in __callchain__fprintf_graph()131 remaining -= cumul; in __callchain__fprintf_graph()
22 14. PROPAGATION ORDER RELATION: cumul-fence829 PROPAGATION ORDER RELATION: cumul-fence833 smp_wmb() fences) are collectively referred to as cumul-fences, even834 though smp_wmb() isn't A-cumulative. The cumul-fence relation is847 and W ->cumul-fence W', then W must propagate to any given CPU1296 followed by an arbitrary number of cumul-fence links, ending with an1300 followed by two cumul-fences and an rfe link, utilizing the fact that1332 store to y does (the first cumul-fence), the store to y propagates to P21335 store to z does (the second cumul-fence), and P0's load executes after the1355 F via a coe or fre link, an arbitrary number of cumul-fences, an[all …]
