public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schneck at math dot berkeley dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/13182] -fstack-check probes too distant when allocating on stack Date: Tue, 25 Nov 2003 13:02:00 -0000 [thread overview] Message-ID: <20031125130246.23999.qmail@sources.redhat.com> (raw) In-Reply-To: <20031125002135.13182.schneck@math.berkeley.edu> ------- Additional Comments From schneck at math dot berkeley dot edu 2003-11-25 13:02 ------- (In reply to comment #1) I fear you may have missed my point. Stack probes are supposed to happen at STACK_CHECK_PROBE_INTERVAL, i.e. 4096. One function does one probe, at sp - 12792 (which is > 4096*3). One function does two probes, one at sp - 4392, the other at sp - 12792 (a difference of > 4096*2). Even if the thread has TWO guard pages this could fail to be safe! Please forgive me if I misunderstand. I had looked at the internals manual, and I understand (I think) why it is correct for the first check to be at sp - 4392. But I am rather convinced that the interval had better be 4096 (or less) thereafter. Robert -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182
next prev parent reply other threads:[~2003-11-25 13:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-25 0:21 [Bug c/13182] New: " schneck at math dot berkeley dot edu 2003-11-25 0:43 ` [Bug c/13182] " pinskia at gcc dot gnu dot org 2003-11-25 13:02 ` schneck at math dot berkeley dot edu [this message] 2003-11-27 17:23 ` pinskia at gcc dot gnu dot org 2003-12-19 2:10 ` [Bug middle-end/13182] " pinskia at gcc dot gnu dot org 2003-12-21 3:20 ` lothar at xcerla dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20031125130246.23999.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).