mirror of
https://git.code.sf.net/p/quake/quakeforge
synced 2024-11-15 01:11:27 +00:00
beb05f28ff
And maybe a nano-optimization. Switching from (~side + 1) to (-side) seems to give glsl a very tiny speed boost, but certainly doesn't hurt. Looking at some assembly output for the three cases, the two hacks seem to generate the same code as each other, but 3 instructions vs 6 for ?:. While ?: is more generically robust, the hacks are tuned for the knowledge side is either 0 or 1. The later xor might alter things, but at least I now know that the hack (either version) is worthwhile. |
||
|---|---|---|
| .. | ||
| glsl_alias.c | ||
| glsl_bsp.c | ||
| glsl_draw.c | ||
| glsl_fisheye.c | ||
| glsl_iqm.c | ||
| glsl_lightmap.c | ||
| glsl_main.c | ||
| glsl_particles.c | ||
| glsl_shader.c | ||
| glsl_sprite.c | ||
| glsl_textures.c | ||
| glsl_warp.c | ||
| qfglsl.c | ||
| quakeforge.glsl | ||
| vid_common_glsl.c | ||