I’ve started noticing articles and YouTube videos touting the benefits of branchless programming, making it sound like this is a hot new technique (or maybe a hot old technique) that everyone should be using. But it seems like it’s only really applicable to data processing applications (as opposed to general programming) and there are very few times in my career where I’ve needed to use, much less optimize, data processing code. And when I do, I use someone else’s library.

How often does branchless programming actually matter in the day to day life of an average developer?

  • lowleveldata@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Can’t imagine any practical difference performance wise. Maybe it’s about making the flow easier to understand? I do recall that Sonarqube sometimes complains when you have too much branchings in a single function

    • Ethan@programming.devOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      If you’re writing data processing code, there are real advantages to avoiding branches, and its especially helpful for SIMD/vectorization such as with AVX instructions or code for a GPU (i.e. shaders). My question is not about whether its helpful - it definitely is in the right circumstances - but about how often those circumstances occur.

      • lowleveldata@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Ya, and my examination is I don’t think it has practical impacts for day to day tasks. Unless you’re writing AVX instructions day to day but then you already knew the answer.