I believe each wavefront has its own instruction pointer. For me, it's easier to think about GPU arch as trying to realize a never-ending stream of data being

I believe each wavefront has its own instruction pointer. For me, it's easier to think about GPU arch as trying to realize a never-ending stream of data being continually processed, with all other components of a processor redefined to ensure The Stream Never Stops. From that perspective, things like wavefront-attached instructions, data scheduling, execution masking, or bastardized conditional support make more sense. Think of "a cycle" as a set of data first, rather than an instruction/state. https://developer.amd.com/wp-content/resources/RDNA2_Shader_ISA_November2020.pdf https://developer.amd.com/wp-content/resources/RDNA2_Shader_...