public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jtc at acorntoolworks dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/18260] generated code uses memory beyond allocated stack frame. Date: Mon, 01 Nov 2004 22:45:00 -0000 [thread overview] Message-ID: <20041101224543.961.qmail@sourceware.org> (raw) In-Reply-To: <20041101000818.18260.jtc@acorntoolworks.com> ------- Additional Comments From jtc at acorntoolworks dot com 2004-11-01 22:45 ------- I seem to have missed the description of the "red-zone" when I read the ABI. It's a neat optimization for leaf functions, but violates the principal of least suprise. I have confirmed that the MySQL4 crashes that we were experiencing went away with -mno-red-zone. I have done further investigation, and it appears that NetBSD/amd64's thread context switch code did not preserve the red-zone until recently. This has been fixed in -current, and hopefully the changes will be pulled up to the release branch before 2.0 is released. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18260
prev parent reply other threads:[~2004-11-01 22:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-01 0:08 [Bug c/18260] New: " jtc at acorntoolworks dot com 2004-11-01 0:11 ` [Bug rtl-optimization/18260] " pinskia at gcc dot gnu dot org 2004-11-01 0:21 ` jtc at acorntoolworks dot com 2004-11-01 13:06 ` falk at debian dot org 2004-11-01 22:45 ` jtc at acorntoolworks dot com [this message]
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=20041101224543.961.qmail@sourceware.org \ --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).