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 In addition, mix() can cause NaN because GPU can calculate 0*NaN=NaN.

@iquilezles In addition, mix() can cause NaN because GPU can calculate 0*NaN=NaN.

Properties5
typearchive
sourcetwitter
date2025-02-10
tagsarchive, twitter, iquilezles
description@iquilezles In addition, mix() can cause NaN because GPU can calculate 0*NaN=NaN.

Feb 10, 20251 min read

  • archive
  • twitter
  • iquilezles

Source

  • URL: https://x.com/ekakiya/status/1888852044645339609
  • Author: Katsuhiko Omori (@ekakiya)
  • Posted: 2025-02-10 07:26:35

Branch

1/ @ekakiya

@iquilezles

In addition, mix() can cause NaN because GPU can calculate 0*NaN=NaN. It stops some optimizations that if() can get.

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