https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114437
--- Comment #3 from xog4n...@a-n.cc --- Just to confirm, is this an incorrect constraint for the intended goal of convincing the compiler that the value is used and modified, without actually doing either and preserving the value, or am I just using it wrong in this particular example? I'm somewhat surprised since this inline asm snippet is used in multiple well-known micro-benchmarking libraries. Is the following version correct? ``` asm volatile("" : "=m,r"(arg) : "0,0"(arg) : "memory"); ```