[Bug target/83302] i386 stack_probe has side effects

matz at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Dec 7 13:34:00 GMT 2017


--- Comment #3 from Michael Matz <matz at gcc dot gnu.org> ---
In any case, this is not something that GCC could do anything about.  A probe
necessarily has to be a write, and writing to something not belonging to own
stack (or guard page) will always have this problem of seemingly destroying
other data.  The non-atomicness of this particular read-mod-write instruction
doesn't enter the picture.

More information about the Gcc-bugs mailing list