Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.23696v1</id>\n    <title>Semantics for 2D Rasterization</title>\n    <updated>2026-03-24T20:14:34Z</updated>\n    <link href='https://arxiv.org/abs/2603.23696v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.23696v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Rasterization is the process of determining the color of every pixel drawn by an application. Powerful rasterization libraries like Skia, CoreGraphics, and Direct2D put exceptional effort into drawing, blending, and rendering efficiently. Yet applications are still hindered by the inefficient sequences of operations that they ask these libraries to perform. Even Google Chrome, a highly optimized program co-developed with the Skia rasterization library, still produces inefficient instruction sequences even on the top 100 most visited websites. The underlying reason for this inefficiency is that rasterization libraries have complex semantics and opaque and non-obvious execution models.\n  To address this issue, we introduce $μ$Skia, a formal semantics for the Skia 2D graphics library, and mechanize this semantics in Lean. $μ$Skia covers language and graphics features like canvas state, the layer stack, blending, and color filters, and the semantics itself is split into three strata to separate concerns and enable extensibility. We then identify four patterns of sub-optimal Skia code produced by Google Chrome, and then write replacements for each pattern. $μ$Skia allows us to verify the replacements are correct, including identifying numerous tricky side conditions. We then develop a high-performance Skia optimizer that applies these patterns to speed up rasterization. On 99 Skia programs gathered from the top 100 websites, this optimizer yields a speedup of 18.7% over Skia's most modern GPU backend, while taking at most 32 $μ$s for optimization. The speedups persist across a variety of websites, Skia backends, and GPUs. To provide true, end-to-end verification, optimization traces produced by the optimizer are loaded back into the $μ$Skia semantics and translation validated in Lean.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.PL'/>\n    <published>2026-03-24T20:14:34Z</published>\n    <arxiv:comment>23 pages, 15 figures</arxiv:comment>\n    <arxiv:primary_category term='cs.PL'/>\n    <author>\n      <name>Bhargav Kulkarni</name>\n    </author>\n    <author>\n      <name>Henry Whiting</name>\n    </author>\n    <author>\n      <name>Pavel Panchekha</name>\n    </author>\n  </entry>"
}