Searched refs:fly (Results 1 - 9 of 9) sorted by relevance

/xsrc/external/mit/mesa-demos/dist/src/trivial/
H A Dtri-stipple.c34 static GLubyte fly[] = {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, variable in typeref:typename:GLubyte[]
57 glPolygonStipple (fly);
H A Dtri-tex-stipple.c10 static GLubyte fly[] = {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, variable in typeref:typename:GLubyte[]
57 glPolygonStipple (fly);
/xsrc/external/mit/mesa-demos/dist/src/redbook/
H A Dpolys.c51 GLubyte fly[] = {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, local in function:display
85 glPolygonStipple (fly);
/xsrc/external/mit/MesaLib/dist/docs/relnotes/
H A D12.0.4.rst240 - st/glsl_to_tgsi: disable on-the-fly peephole for 64-bit operations
H A D19.0.0.rst1311 - spirv: Emit NIR deref instructions on-the-fly
1355 - spirv: Emit switch conditions on-the-fly
H A D19.1.0.rst455 - panfrost: Compute viewport state on the fly
/xsrc/external/mit/MesaLib/dist/src/amd/compiler/
H A DREADME.md89 The register allocator works on SSA (as opposed to LLVM's which works on virtual registers). The SSA properties guarantee that there are always as many registers available as needed. The problem is that some instructions require a vector of neighboring registers to be available, but the free regs might be scattered. In this case, the register allocator inserts shuffle code (moving some temporaries to other registers) to make space for the variable. The assumption is that it is (almost) always better to have a few more moves than to sacrifice a wave. The RA does SSA-reconstruction on the fly, which makes its runtime linear.
/xsrc/external/mit/ctwm/dist/
H A DCHANGES.md673 edit the labels of workspaces on the fly (what use this is, I'm not
/xsrc/external/mit/ctwm/dist/doc/manual/
H A Dctwm.1.adoc1556 or +|command+ for an on the fly generated xwd file. Use the % character

Completed in 21 milliseconds