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 But if I use that doesn’t that result in a time when the compiler uses a separate instance to do the effects that would have been done in a different way otherwise? Hypothetically, if you consider the end effects

@iquilezles But if I use that doesn’t that result in a time when the compiler uses a separate instance to do the effects that would have been done in a different way otherwise? Hypothetically, if you consider the end effects

Properties5
typearchive
sourcetwitter
date2025-02-09
tagsarchive, twitter, iquilezles
description@iquilezles But if I use that doesn’t that result in a time when the compiler uses a separate instance to do the effects that would have been done in a different way otherwise? Hypothetically, if you consider the end effects

Feb 09, 20251 min read

  • archive
  • twitter
  • iquilezles

Source

  • URL: https://x.com/UnderwaterBepis/status/1888627023414759796
  • Author: Bepis™ 🔀🫛 (@UnderwaterBepis)
  • Posted: 2025-02-09 16:32:26

Branch

1/ @UnderwaterBepis

@iquilezles

But if I use that doesn’t that result in a time when the compiler uses a separate instance to do the effects that would have been done in a different way otherwise? Hypothetically, if you consider the end effects

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