public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/27234] no way to stop gcc from mucking with the stack Date: Fri, 21 Apr 2006 03:19:00 -0000 [thread overview] Message-ID: <20060421031946.26055.qmail@sourceware.org> (raw) In-Reply-To: <bug-27234-12219@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gcc dot gnu dot org 2006-04-21 03:19 ------- Did you know sibcalling reduces the stack usage in fact it is kinda stupid to have a function call overhead to create a stack? Therefor the asm should instead create the stack. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27234
next prev parent reply other threads:[~2006-04-21 3:19 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-21 2:22 [Bug c/27234] New: " acahalan at gmail dot com 2006-04-21 2:35 ` [Bug c/27234] " pinskia at gcc dot gnu dot org 2006-04-21 3:16 ` [Bug target/27234] " acahalan at gmail dot com 2006-04-21 3:19 ` pinskia at gcc dot gnu dot org [this message] 2006-04-21 3:41 ` acahalan at gmail dot com 2006-04-22 20:24 ` pinskia at gcc dot gnu dot org 2006-04-22 20:35 ` [Bug target/27234] no way to stop gcc from mucking with the incoming argument stack rguenth at gcc dot gnu dot org 2006-04-22 21:09 ` schwab at suse dot de 2006-04-22 23:28 ` joshudson at gmail dot com 2006-04-23 2:05 ` acahalan at gmail dot com 2006-04-23 2:09 ` acahalan at gmail dot com 2006-04-23 2:13 ` pinskia at gcc dot gnu dot org 2006-05-01 4:51 ` ian at airs dot com 2006-05-01 5:58 ` pinskia at gcc dot gnu dot org 2006-05-02 3:40 ` ian at airs dot com 2008-04-10 17:41 ` jakub at gcc dot gnu dot org 2008-04-10 18:10 ` [Bug target/27234] no way to stop gcc from mucking with the incoming argument stack on ia32/x86_64 jakub at gcc dot gnu dot org 2008-04-10 18:14 ` [Bug target/27234] no way to stop gcc from mucking with the incoming argument stack on ia32 jakub at gcc dot gnu dot org 2008-04-11 10:26 ` jakub at gcc dot gnu dot org 2008-04-24 16:06 ` hubicka at gcc dot gnu dot org 2008-04-29 15:41 ` hubicka at gcc dot gnu dot org
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=20060421031946.26055.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).