Processing order of vertices and fragments in arm gpu

In relatively new GPUs, calculations are done in the order of indexbuff. The vertices shared by multiple triangles may be calculated multiple times.

Yes, may be shaded multiple times but there is post-transform caching, so it will only happen if you have bad locality in your index buffers. In general we don't see much reshading for sensibly ordered meshes.

What about these old GPUs you mentioned? Will there be multiple calculations? In other words, o lder Mali GPUs (Utgard, Midgard) simply render all vertices once in incrementing index order, between min and max referenced index?

It's guaranteed not to reshade, but may shade non-referenced vertices between min and max (various optimizations exists to minimize this, but YMMV). It's therefore recommended to tightly pack used indices - no unreferenced vertex between min and max.

HTH, 
Pete

In relatively new GPUs, calculations are done in the order of indexbuff. The vertices shared by multiple triangles may be calculated multiple times.

Yes, may be shaded multiple times but there is post-transform caching, so it will only happen if you have bad locality in your index buffers. In general we don't see much reshading for sensibly ordered meshes.

What about these old GPUs you mentioned? Will there be multiple calculations? In other words, o lder Mali GPUs (Utgard, Midgard) simply render all vertices once in incrementing index order, between min and max referenced index?

It's guaranteed not to reshade, but may shade non-referenced vertices between min and max (various optimizations exists to minimize this, but YMMV). It's therefore recommended to tightly pack used indices - no unreferenced vertex between min and max.

HTH, 
Pete