galley_formatter
Output format selection matching Galley's physical optimizer.
This is a direct port of select_output_format from
src/Galley/PhysicalOptimizer/format-selector.jl in Finch.jl. The Julia
version stores levels innermost-index-first and therefore walks the output
indices back to front; here index_order[0] is the outermost level, so the
walk runs front to back and the resulting formats need no reversal.
GalleyFormatter
Bases: LogicFormatter
A formatter which picks output formats the way Galley's physical optimizer does, choosing per level between dense, bytemap, hash, and sparse list based on the estimated sparsity of the output and the loop order it is built under.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 | |
LevelFormat
Bases: Enum
The level formats Galley's format selector chooses between.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 | |
estimate_nnz(stats, stats_factory, indices)
Estimate the number of non-fill values of stats projected onto indices.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
92 93 94 95 96 97 98 99 100 101 102 103 | |
fully_compat_with_loop_prefix(tensor_order, loop_prefix)
Whether tensor_order can be written sequentially under loop_prefix.
Both are given outermost first. A tensor deeper than the loop prefix is still compatible; a mismatch at any shared position is not.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | |
query_loop_order(rhs)
The loop order a query's right hand side is evaluated under.
Loop orders are carried by the Reorder node interior to an aggregate, or
at the root of an in-place update; a transpose query is looped in the order
its input is stored.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 | |
select_output_format(stats, stats_factory, loop_order, output_indices)
Choose a level format for each of output_indices, outermost level first.
loop_order is the loop order the output is built under, also outermost
first. Levels which cannot be filled in loop order need random writes and
so fall back to a hash level rather than a sparse list.
Source code in src/finch/autoschedule/formatter/galley_formatter.py
106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 | |