Zynq Ultrascale MPSoC task floating point corruption

Understood. Thanks for that clarification. By “common cases” I meant “scenarios where application developers are commonly going to use memcpy()/memcmp()/etc”, which has a built in assumption that it’s to act on large blocks of data. That assumption is entirely just an assumption and perhaps is wrong.

In a related vein, I stumbled on this thread GCC9 compiled code damage function local variable (related to VFP/FPU support) - #5 by jdobry which makes me think that it’s not really as simple as only the tasks that use FPU instructions competing with ISRs that also use FPU instructions.