This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/83302] i386 stack_probe has side effects
- From: "matz at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 07 Dec 2017 13:34:27 +0000
- Subject: [Bug target/83302] i386 stack_probe has side effects
- Auto-submitted: auto-generated
- References: <bug-83302-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83302
--- 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.