Threadwell

Recent Notes

  • JohannesVuorine

    Aug 26, 2026

    • archive
    • twitter
    • johannesvuorine
  • Threads

    Aug 26, 2026

    • archive
  • iquilezles

    Aug 26, 2026

    • archive
    • twitter
    • iquilezles
Home

❯

Archive

❯

Threads

❯

iquilezles

❯

Hey, don't "optimize" conditional moves with mix()+step().

❯

@iquilezles I suspect the reason for the poor advice stems from the beginning of programmable shaders on mobile.

@iquilezles I suspect the reason for the poor advice stems from the beginning of programmable shaders on mobile.

Properties5
typearchive
sourcetwitter
date2025-07-30
tagsarchive, twitter, iquilezles
description@iquilezles I suspect the reason for the poor advice stems from the beginning of programmable shaders on mobile.

Jul 30, 20251 min read

  • archive
  • twitter
  • iquilezles

Source

  • URL: https://x.com/SquaredApe/status/1950549491163246681
  • Author: Robert William Cummings (@SquaredApe)
  • Posted: 2025-07-30 13:30:12

Branch

1/ @SquaredApe

@iquilezles

I suspect the reason for the poor advice stems from the beginning of programmable shaders on mobile. Back then, branches were very expensive, a combination of early compilers and hardware.

Much has changed in 20 years or more :)

Related

  • Spine: 2025-02-09-hey-dont-optimize-conditional-moves-with-mix-step

Graph View

  • Source
  • Branch
  • Related

Backlinks

  • Hey, don't "optimize" conditional moves with mix()+step().

Created with Quartz v5.0.0 © 2026

  • GitHub