On Fri, 16 Dec 2022 12:19:47 -0500 Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > I assumed that "memory" was for memory unrelated to the input constraints. Well, it looks like you do need a "memory" barrier. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html "memory" The "memory" clobber tells the compiler that the assembly code performs memory reads or writes to items other than those listed in the input and output operands (for example, accessing the memory pointed to by one of the input parameters). To ensure memory contains correct values, GCC may need to flush specific register values to memory before executing the asm. Further, the compiler does not assume that any values read from memory before an asm remain unchanged after that asm; it reloads them as needed. Using the "memory" clobber effectively forms a read/write memory barrier for the compiler. As the "(for example, accessing the memory pointed to by one of the input parameters)" is exactly this case. -- Steve
